How to Fix AWS DNS Record Propagation Issues After 5 Days

Select Language:

It sounds like you’re facing a common problem: your A, AAAA, and NS records are updating fine, but the MX and CNAME records aren’t showing up everywhere, even after five days. This usually points to a problem with how your domain’s nameservers are set up, rather than just a delay in DNS propagation.

Here’s how to fix it:

First, double-check that the nameservers listed in your domain registration match exactly with those in your Route 53 hosted zone. Even a small mismatch can cause some records not to update everywhere.

Next, look to see if you have more than one hosted zone for the same domain. If there’s more than one, it can confuse the servers, making some parts of your DNS not work correctly.

Also, make sure your domain’s glue records are correct. These are important to connect your domain to your DNS provider properly, especially if you’re using custom nameservers.

To verify that your MX and CNAME records are correct, use command-line tools like dig or nslookup. For example, to check your MX records directly against your AWS nameservers, run this:

dig MX yourdomain.com @ns-xxx.awsdns-xx.com

If this returns the right records, but other tools aren’t showing them globally, it’s likely your nameserver info is not set up correctly.

Then, go to your Route 53 console. Under your domain settings, find the option to edit your nameservers and make sure they match the ones in your hosted zone. If they don’t, update them to the correct set.

Since your A and AAAA records are working but MX and CNAME are not, it points to a mismatch or misconfiguration in your nameservers. During domain transfers or changes, this can happen, so ensure everything matches.

If you’ve checked all of this and are still having trouble, reaching out to AWS Support can give you detailed help tailored to your situation. They’re experts and can troubleshoot further if needed.