Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Amazon AWS Route 53 Hosted Zone does not work

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?

like image 618
DanielRoberts Avatar asked Mar 13 '16 12:03

DanielRoberts


People also ask

Which is a function that Amazon Route 53 does not perform?

Amazon Route 53 does not have a default TTL for any record type. You must always specify a TTL for each record so that caching DNS resolvers can cache your DNS records to the length of time specified through the TTL.

How do I change my hosted zone on Route 53?

You can't convert a public hosted zone to a private hosted zone or vice versa. Instead, you must create a new hosted zone with the same name and create new resource record sets. For more information about charges for hosted zones, see Amazon Route 53 Pricing .


2 Answers

You have successfully transfered the domain to Gandi, but your domain is still configured with GD nameservers. Check this:

  1. Log in to your AWS web console
  2. Select Route53 service
  3. Select Hosted Zones in the left pane
  4. Select verticeinteractive.co.uk (but do not click on the domain name, just select the radio button)
  5. Notice the 4 name servers in the right pane.
  6. Next, go to domain registrar site (in your case stay in Route53), log in and configure name servers for your domain. In Route53: select 'Registered domains' in the left pane, click on your domain name, verify that in the upper right you have name servers from step 5, if they don't exactly match, click 'Add/Edit Name servers' and enter name servers from step 5)
like image 135
Dusan Bajic Avatar answered Sep 25 '22 23:09

Dusan Bajic


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.

like image 38
Rene B. Avatar answered Sep 21 '22 23:09

Rene B.