Amazon AWS Route 53 Hosted Zone does not work

user_5921948 0
Viewed 21616

So I have moved my domain over to Amazon Route 53 and I have made a new hosted zone with all of the correct records, yet when I go to my domain, it gives me the error

dial tcp: lookup verticeinteractive.co.uk on 8.8.4.4:53: server misbehaving

and whenever I use a DNS lookup tool, it says it does not have any aliases. name servers or mail exchange records. It has not yet been 48 hours since I transferred it, but it has been at least 36 hours and I have cleared my DNS cache which allowed this error message to come up.

Any ideas?

amazon-route53 amazon-web-services dns amazon-s3
6 Answers

I had a mismatch of the domain servers between the registered domain and the Hosted zones.

To solve this you should copy the domain name server from Route 53 -> Hosted zones:

enter image description here

to:

Route 53 -> Registered domains -> Name servers:

enter image description here

However, the management console didn't show me the correct domain servers in the Hosted zones filed. Therefore, I had to use the aws-cli as follows:

aws route53 list-hosted-zones
aws route53 get-hosted-zone --id <ID_OF_ZONE>

This returned the list of name servers that the hosted zone was using. Copy this list into the Registered domains section of Name Servers.

Afterwards, my A recorded started without any issues.

user_89006830

Just a note for those that have Route 53 domains that are not resolving, but passing the "Check Record Set".

This can be because your NS Records in your "Zone Information" and "Registered Domains" are different than what was assigned.

The name servers are assigned and can be looked at by clicking the radio button under "Hosted Zones".

Open a new window, and click on "Registered domains". Then click on your domain. In the upper right, there is a list of Name Servers. Those must match the ones assigned.

(Just changing the NS Records in the Hosted Zone page isn't enough.)

If there is a difference, click on the Add or Edit Name Servers under Regstered Domains. Add them one at a time into the table.

Click modify and you should see them start working... You can check on https://dnschecker.org/

user_28087520

If you replaced the automatically generated Hosted Zone, don't forget to go under "Registered domains", select your domain and then click on "Add or edit name servers". It is a small link under the list of nameservers associated to your domain, if they still match the ones of your old hosted zone you should change them with the new ones.

user_27013480

The following works for me:

foo.com : Top level hosted zone (Registered / transfered domain) foo.com NS records points to NS's allocated in registered domains.

sub1.foo.com : hosted zone NS record points to delegated NS's (assigned by AWS)

To resolve sub1.foo.com externally create a copy of its NS record in the foo.com hosted zone.

foo.com now has two NS records:

foo.com NS record

sub1.foo.com NS record

user_170506660

For posterities sake I'll give my experience.

I transferred domains from one AWS account to another and had mismatched name servers on the domain and hosted zones. In this case, follow the instructions above or just copy the name servers from the hosted zone onto the domain.

user_26200510
Related