Migrating MX Records

Posted on 2012-08-27
Medium Priority
Last Modified: 2012-08-29
I am deploying a new email gateway that will handle TLS and web based email delivery, really all email delivery to/from my company.  Previously I was running exchange only.  I am planning the migration and am trying to decide on the best way to handle DNS(MX) records.  Currently mail is delivered to mail.domain.com, mail2.domain.com, and mail3.domain .com with pref.s of 10, 20, and 30 respectively.  All point via different ISP's to the same mail server internally named mail.domain.com.  My thought was to name the new mail proxy smail.domain.com (and get an SSL cert for said name).  I could create public A & MX records with MX preferences of 15, 25, and 35 for smail, smail2, smail3. Thus until I took exchange out of line for direct email delivery, it would be attempted first.  Once the gateway is up and tested, I could remove the mail.domain.com records from the MX list.  I’m just running this by to be sure I’m not missing something obvious and disastrous.  Would this work?
Question by:whoam
  • 2
LVL 33

Accepted Solution

Exchange_Geek earned 2000 total points
ID: 38339059
This would definitely work, however ensure that post each DNS Change you are giving atleast 72hrs for changes to be replicated across to the internet AND ensure that you're ISP guy has made rules that doesn't surprise you.

LVL 20

Expert Comment

ID: 38347577
The 72 hours given by Exchange_geek should actually rather be taken to be a combination of TTL and SOA entries in your DNS. However, due to the special nature how mail servers treat MX records, you may decommission the old MX records at will - the main effect is rather the deactivation of the mail server.

I have one feedback question though: Do I understand correctly that you do have three different MX entries because of three redundant uplinks, but there is not actually a backup servre? That is, if your mail server is down, all three MX fail at once?

Author Closing Comment

ID: 38348000

Author Comment

ID: 38348007

Good observation, yes only one mail server instance exists so if it fails, all 3 IP's would stop taking smtp.  However, it's virtual on multiple physical hosts and regularly backedup and "snapshotted" on shared storage so could be kick-started quickly.  When we go Exch'13 we'll re-do with multiple front-ends etc. which will be a better design.  Just don't have the budget right now.

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The most common mistakes I hear or read about email usually begin with people talking about POP3 and IMAP, so let's clear those off the table: POP3 and IMAP have absolutely nothing to do with sending or receiving email, so get that notion out of you…
Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
This Micro Tutorial will teach you how to add a cinematic look to any film or video out there. There are very few simple steps that you will follow to do so. This will be demonstrated using Adobe Premiere Pro CS6.
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month14 days, 3 hours left to enroll

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question