CODEWITHSUNDEEP
amazon-web-servicesdnsamazon-route53
Daniel Apt
Daniel Apt

Reputation: 2638

DNS hosted zone not taking effect - AWS Route53

I have recently transferred my domain name trademarklawexplained.com from One.com to AWS.

I have the following set-up in Route53:

Route53 Hosted Zone set-up

For some reason, none of my records (SOA, NS and A) have had any effect. trademarklawexplained.com does not map to 35.176.22.92, nor does it even look at the name server (I tested it with this tool)

Have I set up my hosted zone incorrectly, should I somehow publish it, or is the issue with One.com?

If someone could point me in the right direction to troubleshoot it would be greatly appreciated.

Upvotes: 3

Views: 3339

Answers (4)

ravishankar d
ravishankar d

Reputation: 1

i have encountered a similar issue, i had to wait for about 2 days to get the A record have a correct routing. However, the A record of alias type to the load-balancer works almost immediately.

Upvotes: 0

Daniel Apt
Daniel Apt

Reputation: 2638

Figured it out in the end…

For a name server to be associated with a Route53 hosted zone, do the following:

  1. Create a Hosted zone for your domain name. Note the NS record.
  2. Go to Registered Domains > example.com > Add or edit name servers > Add the name servers from step 1.

Select your registered domain on AWS Route53 Edit name servers

When transferring a domain to AWS, it keeps the old NS record. Make sure to change it as per step 2.

Upvotes: 12

John Hanley
John Hanley

Reputation: 81336

How long have you waited? DNS records have a TTL (Time To Live). DNS servers around the world will cache your domain records until the TTL expires. For example, in your screenshot the TTL for your Name Servers is 172800 seconds which is 48 hours. In general it takes two or three days for the Internet to start caching your new domain records, sometimes longer. If it has been more than a week, then there is a problem.

Upvotes: 0

Kannaiyan
Kannaiyan

Reputation: 13025

Checking the records it is still pointing to old records.

You need to update the DNS servers with your domain registrar for it to take effect.

If the DNS servers are updated, you might need to wait for the TTL time defined with the previous registrar to expire. DNS servers can cache those records until that TTL time defined in those NS records.

Upvotes: 1

Related Questions