Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am changing webhosts and will be using the new hosts mail servers instead of the old ones.

I have created all the correctly named mailboxes on the new service but have also not yet cut ties with the old webhost. I am expecting that even if the new DNS values which point to the new hosts DNS servers and respective SOA\zone file with the new MX values have not yet propagated and an E-mail is directed at the old hosts mail servers as per the mx records in the SOA\zone records which the old hosting provider holds, the E-mail would still come through to the mailbox that's on the old host providers mail servers. So I am just trying to reaffirm if I got this right and it's essentially impossible for me to loose an E-mail since it will hit either the old hosts mail servers or the new ones ?

Also is it possible to configure the same E-mail account to check and collect mail from different mail servers by entering multiple pop3 addresses ? And if I choose to keep the old web hosts mail hosting services as a backup by specifying the mx records for it with a lower priority in the SOA records hosted by the new webhost, is it possible to have any incoming E-mails sent to both servers by the mail daemon so I have two copies? Or is my only option having the primary mail server forward the E-mail somehow to the old mailserver ?

share|improve this question
    
If you're considering keeping the old email provider as a backup why not just continue to use them for email hosting rather than moving your email? There's no technical reason you have to move your email hosting with your web hosting. –  joeqwerty Oct 2 '12 at 3:48
    
@joeqwerty The new mailserver(s) are a tad faster, offer more space and some advanced syncing options that I may take advantage off. Otherwise yeah I could just stick the old mail servers MX records with highest priority into the zone file on the new hosts DNS servers. –  LaserBeak Oct 2 '12 at 3:51
add comment

1 Answer

up vote 5 down vote accepted

After the new mail server is ready to accept mail for your domain via smtp and serve mail via imap and or pop or the like, then you want to change the old server to forward mail to the new server. Get all this working BEFORE you change MX records. Then it doesn't matter if mail arrives at either the old or new server, since it all ends up at the new server, eventually.

I dislike people using the term "propagation" when referring to most DNS changes, as I find that most people are being mislead to what is going on. Typically DNS changes are instantaneous, there is no need for propagation. Propagation only happens when you are changing the nameservers at the registrar, and these changes need to go out to all the root DNS servers. This is an operation that used to take many hours in the (distant by internet standards) past, but no longer takes much time. These days when people talk about propagation, they are usually incorrectly referring to DNS TTLs.

Whenever an authoritative nameserver answers a DNS question (like what are the mx records for this domain), that answer comes with a TTL, which says "here is your answer. You can assume this answer is the correct answer for X seconds". So if you have a very long TTL on your MX records, and then change them. People that looked up your MX records might cache the results for a long time, and therefore, after the change, will be sending mail to the wrong server for a long time. If you are anticipating a change in DNS records. You can drop the TTL to something small until after the change.

share|improve this answer
1  
Very good answer. Thanks for explaining the DNS bit. I can't tell you how many times I cringe at the phrase "DNS propagation". The only thing I would correct is that the root name servers and the gTLD servers are different servers, serving different portions of the DNS namespace. The root servers (a.root-servers.net, etc.) know nothing about third level domains (google, microsoft, etc.). The gTLD servers (a.gtld-servers.net, etc.) responsible for the specific gTLD (the second level domains such as .com, .net, etc.) are the servers that will get the updated NS records for the OP's domain. –  joeqwerty Oct 2 '12 at 4:12
    
Let me get this right, so just set up a simple mail forward, one that does not change the (envelope sender) field to forward mail from an E-mail account on the old host to the one on the new host? Given that the same mailbox names exists at both ends, wouldn't that mean I would be forwarding to the same E-mail i.e. From sameuser@samedomain.com on old host to sameuser@samedomain.com on new host (That's even if it hits the new host, else it will come back to the point of origin if old records have not expired ?) Or perhaps you are referring to some other mail forward method ? –  LaserBeak Oct 3 '12 at 5:48
    
I'm saying to make the old server act as if it were a secondary MX. "Accept any mail for this domain, then just tag on your Received header and move it along to the primary MX" –  stew Oct 3 '12 at 18:39
    
@stew I see though I don't think my shared hosting provider lets me do such mailserver forwards as I see no options in the control panel for either mailboxes or DNS to do so. I can but stick the old hosts MX records with a lower priority into the zone file hosted on the new hosts DNS servers and this will then act as secondary/backup MX records. –  LaserBeak Oct 4 '12 at 1:37
add comment

Your Answer

 
discard

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.