Skip to content

route53 not updating DNS

0

I transferred 3 domains from another registrar and moved it to AWS. 1 is working fine but the other 2 are not.

When I do a NSlookup, no IP comes out. The name servers are listed under the hosted zone details, they are correct. It has the correct IP and the name servers are correct too. It's been more than 2 weeks since I moved them and they will not update.

What am I missing? I tried removing the IP and re-adding it but I still get the same. No IP in nslookup. I'm using different NSlookups and all come back with no IP.

asked a year ago115 views
1 Answer
0

Based on your description, there are several potential issues that could be causing your DNS problems after transferring domains to Route 53:

  1. Nameserver mismatch: Even though you see the correct nameservers in your hosted zone, you need to verify that the domain's registration settings have the same nameservers. When transferring domains, the nameservers don't always automatically update to match your Route 53 hosted zone nameservers.

  2. Glue records: You may need to update the glue records in Route 53 to point to your new nameservers. This is a common issue when transferring domains - the NS records might point to your old registrar's nameservers even after the transfer is complete.

  3. Domain verification: Check if your domains require verification. Sometimes domains can be suspended due to non-verification, and notification emails about this might go to spam folders.

  4. Check both locations: In the Route 53 console, check both:

  • The "Registered domains" section to verify the nameservers assigned to your domain
  • The "Hosted zones" section to confirm your DNS records are properly configured
  1. DNS propagation: While DNS typically propagates within 48 hours, sometimes issues can persist longer. However, after 2 weeks, this is unlikely to be the cause.

To resolve this:

  • In the Route 53 console, go to "Registered domains" and select your problematic domains
  • Check if the nameservers match exactly with those in your hosted zone
  • If they don't match, edit the nameservers to match your hosted zone's nameservers
  • Verify there are no pending domain verification requirements
  • Ensure all necessary DNS records (A records, etc.) are correctly configured in your hosted zone

If these steps don't resolve the issue, you may need to contact AWS Support for further assistance with your specific domain configuration.
Sources
Domain transferred to route53 but not propagated after five days | AWS re:Post
Name Server has not correctly transferred from UK2 to AWS Route53 | AWS re:Post
Route 53 DNS stopped propagating | AWS re:Post
Dns Check after domain move shows only half success | AWS re:Post

answered a year ago
AWS
SUPPORT ENGINEER
reviewed a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.