Domain name not accessible even though Public IP is correct
Hello, I purchased a domain name thru AWS a few days back and it has been working fine. I started an EC2 instance today. I updated the Route 53 A record with the public IP of the EC2 instance but the domain name is not accessible. I did a nslookup, dig, ssh(port 22 is open), but nothing is working. Please see the screenshots below and let me know if I'm missing something. This appears to be a Route 53 issue in my opinion and can only be resolved by AWS. Route 53 says it has propagated the IP and the status says 'INSYNC'.
- Newest
- Most votes
- Most comments
Doing a WHOIS search results in the following: https://registrar.amazon.com/whois?domain=saibisahealingapp.com
Domain Name: saibisahealingapp.com
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: https://registrar.amazon.com
Updated Date: 2023-11-09T12:16:37Z
Creation Date: 2023-10-25T17:41:48Z
Registrar Registration Expiration Date: 2024-10-25T17:41:48Z
Registrar: Amazon Registrar, Inc.
Domain Status: clientHold https://icann.org/epp#clientHold
If Amazon Route 53 suspends your domain, the domain becomes unavailable on the internet.
Follow the steps on : My domain is suspended (status is ClientHold) https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/troubleshooting-domain-suspended.html
Once domain is unsuspended, while creating the Hosted Zone, Confirm that the Name Servers listed in the hosted zone details are identical to the Name Servers in the whois output. This is one of the common causes for "NXDOMAIN" error you saw on the output previously.
Troubleshooting NXDOMAIN: https://repost.aws/knowledge-center/route-53-troubleshoot-nxdomain-responses
Relevant content
- asked 2 months ago
- Accepted Answerasked a year ago
- asked 5 months ago
AWS OFFICIALUpdated a month ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thank you very much, Karthikiran and Gary. Sincerely appreciate the help.