Unable to Receive Email Messages on Your Google Apps Custom Domain?

It happened to me when I added a CNAME record for “codecurry.com”.

Simple solution: I deleted the CNAME and used A Record to point my root domain “.codecurry.com” to my hosting server.

CNAME Records use host-names to point to a server, while an A Record uses host’s IP Address to point to a server.

I have been using Google Apps for email of this account since a year without a glitch. But I had to update this domain’s A Records and CNAME. So instead of changing my A Record, I deleted it and created a CNAME record to point to my hosting server. Too bad, Google Apps didn’t like it. Emails sent to me started bouncing back to senders.

Yes, it is possible to add any CNAME Records  even when using Google Apps Custom Domain Email. So it will work if you add sub-domains hello.codecurry.com or files.codecurry.com. It will simply not work if a CNAME is used for the root domain, as in “.codecurry.com”. The root domain should only be pointed to your host server using A Record.

Hope this will help someone facing this issue with Google Custom Domains.

If you need more information, its always available on Google’s Support pages. And for this particular issue, the following page would be a good start:

http://www.google.com/support/a/bin/answer.py?hl=en&answer=52042

Comments

  1. AlweeJuly 7, 2010 at 2:31:00 PM GMT+5:30

    I have an A record for 1 domain and when I removed it, my incoming emails went haywire. I also have several other google apps hosted domain but they do not have any A records at all and they are doing just fine. Please advice me with regards to my experience.

    Alwee
    alwee(at)hotmail(dot)com

    ReplyDelete
  2. AnonymousJuly 7, 2010 at 2:52:00 PM GMT+5:30

    @Alwee you need to add A record back again for your root domain, for example, .codecurry.com (not any sub-domain) - this A reocrd should point to Google's IP address.

    I wonder how your other domains are working. Can you share the domain names?

    ReplyDelete
  3. PriyankaNovember 20, 2011 at 9:52:00 PM GMT+5:30

    HI, I have a similar problem, I have a CNAME RECORD:

    ftp.gspsinfo.com. CNAME gspsinfo.com.

    All other MX Records are added correctly. IS the CNAME Record the reason that I am not able to receive emails?? I am able to send emails from Google Apps.

    What should I do?

    ReplyDelete
  4. Sameer GuptaNovember 21, 2011 at 9:04:00 AM GMT+5:30

    @Priyanka, try changing your CNAME to an 'A' record. Using an 'A' record means you will be using a static IP assigned to you.

    ReplyDelete

Post a Comment

Be relevant. Spammers will be banned.

Popular posts from this blog

Installing ColdFusion on IIS 7 + Configure IIS for ColdFusion in Windows Vista and Windows Server 2008

Image
When installing ColdFusion on Vista or on Windows Server 2008 you may receive HTTP 404.3 Error, similar to this one:HTTP Error 404.3 - Not FoundThe page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.Additionally if you run ColdFusion Web Server Configuration Tool, you will see a message saying that IIS components are being installed and could take between 2 to 5 minutes of time.You can resolve this error by making sure that the two required components of IIS are installed on your system. Namely:ISAPI Extensions IIS Metabase and IIS 6 configuration compatibility.
Click to Read Complete Article »

ColdFusion Manual Configuration & Issues with TCP ports 51011, 51010 and 51800 on IIS and Apache

Image
ColdFusion works by configuring your web server (IIS, or Apache) to execute files with known extensions (.cfm, .cfml, .cfc et al) to run as script. And for doing that ColdFusion comes with a small and important tool called “wsconfig”. Problem: At times, regardless of operating system and the web server you are using, the ColdFusion installation will fail to configure web-server due to your network settings or firewall/security settings. When running wsconfig tool, you may encounter errors similar to the following:Could not connect to any JRun/ColdFusion servers on host localhost. Possible causes: Server not running
- Start Macromedia JRun4 or ColdFusion server Server running
- JNDI listen port in jndi.properties blocked by TCP/IP filtering or firewall on server
- host restriction in security.properties blocking communication with server Snapshot above shows one of the common scenario when wsconfig will not configure IIS.Solution: H…
Click to Read Complete Article »

ColdFusion 9.0.1 Update Now Available

Adobe released update for ColdFusion 9 yesterday. I have installed the update on my server running Windows Server 2008 with IIS 7.

This update now supports running ColdFusion with IIS7 without installing IIS6 Metabase Compatibility. Finally! IIS7 is almost 4 years old!

Download the update from: http://www.adobe.com/support/coldfusion/downloads_updates.html#cf9

Note: If you are running IIS7 with IIS6 Metabase Compatibility, then you'll have to remove IIS6 MC and that will require a restart of the server.

This update is recommended as it includes many bug-fixes and security hot-fixes.
Click to Read Complete Article »