Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is my first post so sorry for any generic formatting that I might be missing.

I'm trying to reduce the amount of configuration changes that our client would need to perform when we move their website around our servers. We plan to host the clients email with Google Apps and I was wondering if this would be a valid scenario to set up DNS to support a different mail provider if we decide to switch from Google to something else.

Basically what I have in mind:

I'd create two CNAME records (the domain is my clients domain here): -> ->

and then the required MX records that Google provides would also be created for

Would this setup cover such scenario that when we want to switch server we only update the DNS and the client does not need any configuration changes on their side? (obviously we still need to keep using pop3 and smpt to keep it compatible but I'm only asking about the DNS changes here)

Thanks for any help

share|improve this question
up vote 0 down vote accepted

You will be fine with the cname records for the pop and imap but if you change from Google down the line you still might have to reconfigure client email programs because Google requires:

Incoming server must be 993, and must use SSL encryption. Outgoing server can use 587, TLS encryption.

It's also a good idea to add spf records and domain keys to avoid your clients emails getting tagged as spam from Yahoo or MSN

If your server uses PHP to send mail for any applications of course you will need to include the hostname and ip address to your spf.

SPF Records: 14400 in TXT "v=spf1 ~all" 14400 in TXT "v=spf1 a mx ?all"
share|improve this answer

These are for the client email program, correct? If so, that should be ok as long as you don't use CNAME records for the actual MX records.

share|improve this answer
Correct. To be to the point all we need is another name for and and I was wondering if we can do that in our DNS and not violate any standards or good practice rules. – lukaszp Sep 21 '10 at 13:19
I don't believe you'll have any problems. – joeqwerty Sep 21 '10 at 23:07

You could CNAME them, but it will cause the SSL certificates to go mad.

share|improve this answer
Good point, I didn't think about that. Thanks – lukaszp Sep 21 '10 at 15:27
There would only be an issue if Google Apps uses an SSL certificate bound to an FQDN at – joeqwerty Sep 21 '10 at 23:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.