- Newest
- Most votes
- Most comments
Hello.
Although NS records can be confirmed in some areas, it seems to be failing in most areas.
If you look at the "whois" command, you will see an NS record, so check that this NS record and Route53's NS record match.
If they match, it is possible that the domain is simply taking time to propagate.
whois astronomylime.com
Domain Name: ASTRONOMYLIME.COM
Registry Domain ID: 2540268421_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: http://registrar.amazon.com
Updated Date: 2023-05-19T00:38:04Z
Creation Date: 2020-06-20T16:29:44Z
Registry Expiry Date: 2024-06-20T16:29:44Z
Registrar: Amazon Registrar, Inc.
Registrar IANA ID: 468
Registrar Abuse Contact Email: abuse@amazonaws.com
Registrar Abuse Contact Phone: +1.2024422253
Domain Status: ok https://icann.org/epp#ok
Name Server: NS-1362.AWSDNS-42.ORG
Name Server: NS-1584.AWSDNS-06.CO.UK
Name Server: NS-485.AWSDNS-60.COM
Name Server: NS-800.AWSDNS-36.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
Thanks for providing an example domain.
Please refer to this document, specifically the To get the name servers for your hosted zone part and make sure the listed name servers are consistent in your registrar. If the domain is registered through Route 53, then follow the steps in To confirm that the domain is using the correct name servers section.
Compete hog wash. There is something deeply wrong with my AWS hosted zone account. Bad file system, bad server, what ever. I’m out of the AWS system. Wasted too much time waiting for this to self correct. If that is even possible. I will host my domains somewhere else. Good by AWS hosting.
Relevant content
- asked 2 years ago
- asked 10 days ago
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago