MX record not updating after 48 hours

Question

I set my route 53 MX records for ravinmaddhatter.com or mail.ravinmaddhatter.com and in the Route 53 portal it is "No Error" i get the correct routing details and everything looks Ok to me. HOWEVER. DNSchecker.org still has no records. It says typically it takes 24 hours to propagate to public records... I have been waiting 48.. Any more debug i can do?

I just feel lost and helpless.

re:Post Agent · Answer

I understand your frustration with the MX record not updating after 48 hours. This can indeed be a complex issue. Here are some steps you can take to debug and potentially resolve the problem:

1. Double-check your MX record configuration in Route 53. Ensure there are no typos and that the format is correct, including any trailing dots if required.

2. Verify that you're updating the correct hosted zone in Route 53. It's possible to have multiple hosted zones with the same domain name, so confirm you're using the right one.

3. Check your domain's nameservers. Make sure the nameservers listed with your domain registrar exactly match those provided by AWS Route 53. A mismatch can cause DNS resolution failures.

4. Use different DNS lookup tools. Some tools may cache old information. Try using alternative tools like IntoDNS or DNS Lookup to get a broader picture of your MX record propagation.

5. Verify that you're using a public hosted zone in Route 53, not a private one.

6. If you're using DNSSEC, try temporarily disabling it to see if that resolves the issue.

7. Check if there are any glue records that need to be updated.

If after trying these steps you're still experiencing issues, it may be worth considering upgrading your AWS support plan to get direct assistance from AWS support, as they can provide more in-depth troubleshooting for DNS configuration issues.

Remember, while 24-48 hours is a common timeframe for DNS propagation, in some cases it can take longer. If you've verified all your settings are correct, sometimes patience is necessary as the changes propagate through the global DNS system.  
**Sources**  
[Email DNS Issues after Transfer to AWS Route 53 | AWS re:Post](https://repost.aws/questions/QUsfch-n-VRkm23IEwygLUrA/email-dns-issues-after-transfer-to-aws-route-53)  
[DNS Propagation Issues with Domain Registered in Route 53 - No Propagation After 48 Hours | AWS re:Post](https://repost.aws/questions/QURi7p9XFnRHWrbQ5hbDejrw/dns-propagation-issues-with-domain-registered-in-route-53-no-propagation-after-48-hours)  
[route53 problem | AWS re:Post](https://repost.aws/questions/QUXRtjq83lR9mGgqIznrtZ6g/route53-problem)

Maddhatter · Answer

Okay I got everything updated as you recommended, now I just see "no sfp record" I have them set, but will wait 24 to see if that changes

Maddhatter · Answer

Looks like it propagated

Robin Ford · Answer

Route53 doesn't normally have these issue and your right to start to look at the DNS from an external perspective.

When I dig into your domain health using https://mxtoolbox.com/emailhealth/ravinmaddhatter.com/ I see a fair number of issues.
The main ones I'd look at is the DNS servers.
It looks like you might have recreated the zone and got new DNS hosts but these do not match the domain registry (local vs parent list).

So steps for DNS Hosts if using R53 as domain registry.
1. Go to R53 console and then hosted zone.
2. Select the public hosted zone for your domain
3. Get the 4 DNS hosts from ns record 
2. Go to Registered domains and select your domain
3. Under Details click the **Actions** button and select **Edit Name Servers**
4. Update the 4 servers to match the 4 from the ns record.
5. Delete any duplicate/stale so you only have these 4
6. Save Changes

To validate do an nslookup against one of the 4 servers. (replace ns-791.awsdns-34.net)
nslookup -q=mx ravinmaddhatter.com *ns-791.awsdns-34.net* 
This will run the query direct on that name server.

If this works, wait day for it to propagate and revalidate with a DNS checker website.

MX record not updating after 48 hours

Relevant content