[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 826
  • Last Modified:

Changing my mx record without losing mail

We are switching from an in-house email system to Google Apps Premier.  Google Apps has a mail gateway function built-in so that I can forward all mail to my 'old' email server if a mailbox for a user isn't found on the Google servers.  This will let me pilot google apps for my workplace.  I have created my account at google apps and setup the pilot program and I'm now at the point it wants me to edit my mx record. (I just took over here less than two weeks ago so bear with me)

It says to add Google as the first MX record.  I looked up our current settings and they are as follows:

0      mail.mail123.com (our mail server)
15      groups.mail123.com (a mail list server)
20      caseyjones.dundee.net (an external mail list manager)
30      caseyjones.dundee.net (an external mail list manager)
40      random.mail123.com (who knows what this is, it actually fails)

My question is... if I add the Google Apps MX record as 0 and and it's setup to forward all mail to mbeabbs.mathsolutions.com and I set mbeabbs.mathsolutions.com as 15.... will there be any chance of losing mail if Google is setup correctly?  

Should I just bump down the other records by 5 each?  

Why would the prior IT person put in the list manager twice?

Google wants me to add the following records:
1 ASPMX.L.GOOGLE.COM.
5 ALT1.ASPMX.L.GOOGLE.COM.
5 ALT2.ASPMX.L.GOOGLE.COM
10 ASPMX2.GOOGLEMAIL.COM.
10 ASPMX3.GOOGLEMAIL.COM.

Is it safe to do this during work hours?

How long does it take an MX record to propagate?
0
norcalty
Asked:
norcalty
2 Solutions
 
endital1097Commented:
When another messagings system attempts to send a message it queries DNS for the MX record and should attempt to connect to the record with the lowest preference first.  By making the change that Google requested all messages will be routed to their systems first unless they are unavailable.  You should also update the record '0 mail.mail123.com' to '15 mail.mail123.com'.  

You don't need to change any of the other MX records and the one that is there twice would just cause delays if the queries got to that level.
0
 
biscuit3Commented:
This is what I would do.

1. I would renumber the mail.mail123.com to 5
2. I would remove the 30 caseyjones.dundee.net and 40 random.mail123.com  (do you use groups?  Probably remove that one too)
3. I would add the google records keeping the numbering above 20

31 ASPMX.L.GOOGLE.COM.
35 ALT1.ASPMX.L.GOOGLE.COM.
35 ALT2.ASPMX.L.GOOGLE.COM
40 ASPMX2.GOOGLEMAIL.COM.
40 ASPMX3.GOOGLEMAIL.COM

5. I would also see if you can change the TTL to say 5 minutes while you are in transition
6. I would wait 72hrs to allow the propogation of the MX records
7. After you have verified your new MX records are out there and you have everything ready to go, change the numbering of the MX records on the google DNS.
 45 mail.mail123.com (our mail server)
46 groups.mail123.com (a mail list server)
50 caseyjones.dundee.net (an external mail list manager)

1 ASPMX.L.GOOGLE.COM.
5 ALT1.ASPMX.L.GOOGLE.COM.
5 ALT2.ASPMX.L.GOOGLE.COM
10 ASPMX2.GOOGLEMAIL.COM.
10 ASPMX3.GOOGLEMAIL.COM

I would make this change perferably over the weekend, but if you were able to change the TTL on the domain, then you more than likely could do it during the day.  But I would monitor the old mail server to ensure no more mail is being delivered to it.  Give it a day or two and then remove the old MX records
5     mail.mail123.com (our mail server)
15      groups.mail123.com (a mail list server)
20      caseyjones.dundee.net (an external mail list manager)



0
 
touchstar-bradyCommented:
No, you will not lose your email.  This is a DNS record, and will not affect the email stored in the mail stores.  (you gotta give me credit for this one, the way that the question was asked!!!!)

As for email CONNECTIVITY, I would do ALL my MX records to point to Google simultaneously.  This will prevent mail from being delivered to two different places as much as possible.  You could turn down the TTL as biscuit3 suggested a few days before the cut over, but I would strongly recommend cutting all at once.  Me, I like to do this at like 1 AM Saturday morning.  It can take up to 48 hours for DNS records to propagate, however it rarely takes that long on small domains, as they are typically not used enough to be cached on many DNS servers.  I have seen MX records change in 5 minutes on small domains.  

Hope this helps.  
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now