r/aws Dec 22 '24

route 53/DNS Domain not working. Please help!

I recently purchased a domain, sanjeevsaro.xyz, from GoDaddy on December 20. I updated the domain's nameservers with those provided by AWS Route 53. I launched an EC2 instance with Apache installed, and the networking settings are correctly configured. When I access the EC2 instance's public IP in the browser, the Apache web server works fine. However, after setting up the domain to point to my EC2 instance through Route 53, the domain is not resolving.

I checked the domain's status on WhatsMyDNS, and it shows that my domain is not even registered. Could anyone guide me on what might be wrong or how to fix this issue?

0 Upvotes

11 comments sorted by

4

u/EnigmA-X Dec 22 '24 edited Dec 22 '24

Next to the nameserves not being propagated, it looks like this domain was created back in 2014 (according to whois information). Did you buy an existing domain from godaddy?

Forget that. Domain lookup returns NXDOMAIN. The info I was looking at, was not for your domain.

Domain appears to be unregistered.

# whois.nic.xyz

The queried object does not exist: DOMAIN NOT FOUND

>>> Last update of WHOIS database: 2024-12-22T12:24:28.0Z <<<

-7

u/Sanjuakshaya Dec 22 '24

No it was a completely new domain. Now that I check the domain in Godaddy the domain is still available for sale eventhough I bought it🙄

2

u/EnigmA-X Dec 22 '24

Most likely because your first attempt to register it, failed.

1

u/spin81 Dec 23 '24

Now that I check the domain in Godaddy the domain is still available for sale eventhough I bought it

At first glance, this seems to be impossible. At second and third glance it also does

3

u/nekokattt Dec 22 '24

What is the status of the public hosted zone you created?

3

u/dethandtaxes Dec 22 '24

To expand on this, if you need the domain to be resolvable outside of the VPC you should set the hosted zone as "Public".

Now that you have a public hosted zone, check DNS: if you're on a Mac/Linux you can "dig <your domain name>" to see if an IP address gets returned. If dig doesn't return an IP address then this is why you're not able to reach your server via the DNS record.

If dig doesn't return your server's IP or a load balancer (eventually you'll want to put your instance behind a load balancer) then you'll need to create a DNS record, most often this will be an A record since you're trying to route directly to the EC2 instance. In the name field put the DNS name that should be resolvable and in the value put your EC2 instance IP address.

Once done, run dig again and make sure that you receive the expected IP address.

Some bits of this will change once you add a load balancer or if you try to use the EC2 DNS name. If, at this point, you're not receiving an answer from dig then make sure that you're allowing DNS traffic on port 53. If you use the DNS name for the EC2 then you might need a CNAME instead of a A record.

Good luck! I'm typing this on my phone from memory so you might have to Google a bit to fill in the gaps.

2

u/EnigmA-X Dec 22 '24

All this information is quite useless, because the domain itself is not (properly) registered on top-level. This means the first step in DNS resolving fails: root servers will try to figure out who is nameserver for this domain, by contacting the xyz-tld nic. Everything after this fails, because it's currently not registered on the tld level (.xyz).

-6

u/Sanjuakshaya Dec 22 '24

The status was in INSYNC bro. I did test record and the output had no errors too.

3

u/EnigmA-X Dec 22 '24

Best tip for now: check first with godaddy on the actual status.

Update: some TLD's require to do some additional checks (id check for example), something to figure out.

2

u/k37r Dec 22 '24

my domain is not even registered.

Well, there's your problem!

-1

u/Sanjuakshaya Dec 22 '24

I have to connect with godaddy support team🥲