Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

New domain is both registered with and hosted at AWS Route 53 but resolution fails

I have registered the domain duhastdiewahl.org at Amazon AWS Route 53. I do it step for step like this:

http://share.pho.to/AAUSM

  1. Create Hosted Zone (NS/SOA-Record default)
  2. Add A-Record to my elastic ip adress for my EC2-Instance

Unfortunately if i ping the adress the name can't be resolved and tools like http://mxtoolbox.com says that the nameservers couldn't be found.

Can anybody tell me what is wrong? Thank you for your support :)

like image 232
Dude420 Avatar asked May 30 '16 20:05

Dude420


People also ask

How long does Route 53 take to register a domain?

Using AWS Route 53, it takes only 10 minutes to get ready to serve web site on a specific domain name you want to use.

Can Route 53 service be used for domains that are not registered in AWS domain registrar?

You can use Route 53 as the DNS service for any domain, even if the TLD for the domain isn't included on the following lists. For more information about Route 53 as a DNS service, see How internet traffic is routed to your website or web application.

Why can't I access my website that uses Route 53 DNS services?

Check if the name servers (NS) configured at domain registrar are the same four authoritative NS records in the domain's Route 53 public hosted zone. Get the name servers for a public hosted zone. Search for your website's domain name using your preferred WHOIS utility (domain registration lookup tool).


1 Answers

Your nameservers are configured incorrectly in Route 53 "Registered Domains" -- they don't match the servers assigned to you in "Hosted Zones."

Route 53 is two different services -- domain registration and DNS hosting -- and the settings between the two of them need to match. One possible cause of a mismatch is deleting and recreating your hosted zone. That wouldn't fix anything, but a lot of people seem to try it anyway. When you do that, it assigns four new name servers do your domain for hosting -- but the registrar service doesn't learn about this, because there's not necessarily a connection between the two services. You could register a domain on one AWS account, and host the DNS on another, if you wanted -- the two "sides" of Route 53 are essentially independent.

To fix:

In the Route 53 console, click Hosted Zones, click your domain, and make a note of the assigned 4 name servers. Don't change anything here.

Click "Registered Domains."

Select your domain.

Choose "add/edit name servers."

Enter the correct values for the assigned Route 53 name servers, which you obtained from the Hosted Zones screen.

like image 111
Michael - sqlbot Avatar answered Oct 07 '22 04:10

Michael - sqlbot



Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!