Different MX records on primary and secondary name servers.

Avatar
altaub
  • updated
  • Answered

Using G Suite with InMotion hosted site. I used the Google MX Wizard on CPanel to change the MX records, but it only updated one of the two name servers. The other still has the old MX record, so mail bounces whenever that name server is being used. When I use DNS Zone Editor, it only shows the updated ones (on 70.39.150.2) not the old one (on 74.124.210.242). I discovered the problem using G Suite's Check MX tool. How do update the MX records on 74.124.210.242?

Pinned replies
Avatar
0
anonymous
  • Answer
  • Answered

Hello! This sounds like an issue of propagation time. Any changes to the DNS can take up to 24 hours to fully propagate. It sounds like the nameserver closest to you already shows the update, while the one farther away had not yet propagated. If it has been over 24 hours since you updated the DNS, and you have verified that there are no unwanted MX records left in the zone editor, I'd suggest contacting our Support Team and requesting that they update your DNS serial number/push the DNS records to force an update. Hope that helps!

Replies 1
Avatar
0
anonymous
  • Answer
  • Answered

Hello! This sounds like an issue of propagation time. Any changes to the DNS can take up to 24 hours to fully propagate. It sounds like the nameserver closest to you already shows the update, while the one farther away had not yet propagated. If it has been over 24 hours since you updated the DNS, and you have verified that there are no unwanted MX records left in the zone editor, I'd suggest contacting our Support Team and requesting that they update your DNS serial number/push the DNS records to force an update. Hope that helps!