Why would a public Route53 hosted zone not be visible?

Question

I have registered a domain name through Amazon and set up a public hosted zone in Route53. Was able to query records successfully over the internet but that has stopped. My zone is still in Route53 and appears to have the correct records. I followed the diagnostics suggested here and see that the whois records correctly indicate that Amazon is the registrar and there is a match between the whois and Route53 the name server records but when I run a dig +trace privatedataservices.com the connection between the .com nameservers and amazon is absent.

I don't believe I've done anything wrong but my Route53 zone isn't queryable. How should I proceed?

I don't believe I've done anything wrong but my Route53 zone isn't queryable.  How should I proceed?

Answer

It sounds like there may be an issue with the delegation of your domain to the Amazon name servers. A "dig +trace" command is used to trace the path of a DNS query from your local machine to the root DNS servers, and it appears that the connection between the .com nameservers and Amazon is missing in your case.

To resolve this issue, you should first verify that the name servers listed in the WHOIS records for your domain match the name servers in your Route53 hosted zone. If they match, the next step would be to check the delegation of your domain by performing a "dig NS yourdomain.com" command. This should return the name servers that are authoritative for your domain. If the name servers returned by this command do not match the name servers in your Route53 hosted zone, then there is a problem with the delegation of your domain.

You should contact the registrar of your domain and inquire about the delegation of your domain. You can also check the registrar's documentation to see if there is any guidance on how to fix the delegation issue.

Why would a public Route53 hosted zone not be visible?

Relevant content