Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Domain name and route53 issue

I'm having difficulties configuring my domain through Route53. I keep getting a DNS_PROBE_FINISHED_NXDOMAIN error.

My domain, oscha.jp, is registered through jp-domains.com.

I created a hosted zone in R53 and added an alias record pointing to my (test) server. I then logged into jp-domains.com and updated the nameservers to match those in R53.

Using pingdom.com DNS check tool, I have confirmed that my domain is using the correct AWS nameservers.

I have also checked the traceroute for my alias (test.oscha.jp) and I can see that it is routing to the correct IP address. However, putting test.oscha.jp in a browser returns DNS_PROBE_FINISHED_NXDOMAIN.

What can I do to fix this?

like image 495
beterthanlife Avatar asked Mar 11 '16 13:03

beterthanlife


People also ask

Why is Route 53 not working?

If your previous registrar offered free DNS service with domain registration, the registrar might have stopped providing DNS service when you transferred domain registration to Route 53.

What is the difference between Route 53 and DNS?

Your DNS is the service that translates your domain name into an IP address. AWS Route 53 is a smart DNS system that can dynamically change your origin address based on load, and even perform load balancing before traffic even reaches your servers.


2 Answers

You may have just been checking too soon - the site resolves fine for me and it looks like it is using R53 nameservers. Maybe try from another machine/network and/or wait a while and check again.

DNS propagation happens pretty fast, but its not instantaneous.

like image 90
E.J. Brennan Avatar answered Sep 23 '22 18:09

E.J. Brennan


I was having this same issue, but it wasn't a TTL issue for me. The issue I was having was that I had deleted my Hosted Zone and created a new one with what I thought were the same settings. However, I hadn't copied over my new NS addresses (I also have the domain registered through AWS), so the domain was still pointing to the old ones.

If this is the case, also make sure to go into Registered Domains (if you also have your address registered through AWS) or wherever else you have your name server configuration in the service you do have your domain registered.

like image 28
cchapman Avatar answered Sep 22 '22 18:09

cchapman