- Newest
- Most votes
- Most comments
Hello.
Is your domain hosted on Route53?
If you are hosting on Route53, you can open a case with AWS Support under "Account and billing" and they may be able to help you.
Inquiries under "Account and billing" can be made free of charge.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-contact-support.html
By the way, are the registered NS records correct?
You can check the contents of the NS record by opening the hosted zone screen and selecting "Hosted zone details."
It is also a good idea to check whether the NS record matches the "whois" content.
Hello Alex,
Check These steps try to resolve issue,
Verify Name Server (NS) Update:
- Check if the NS records you added at your domain registrar match the ones provided by Route 53. You can find them in the Hosted Zone details section of the Route 53 console.
- Use a tool like dig or nslookup to verify that the new NS records are propagating. It can take up to 48 hours for DNS changes to fully propagate globally, but 4 days should be enough for most cases.
Domain Registration Verification:
If you recently transferred your domain registration to Route 53, ensure you confirmed the email sent by ICANN for verification. A suspended domain won't resolve properly.
For more info follow the links to understand and resolve the issue:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/troubleshooting-route-53.html
Here are some additional tips:
- Be methodical in your troubleshooting. Try each step one at a time and document your findings.
- Make sure you have the correct permissions to manage DNS records for your domain.
- Double-check for typos or errors in your DNS record configuration.
Yes I have added NS from Route 53 to my domain but NS are not propogated yet since 4 days. So what should I do in that case? I checked with https://www.whatsmydns.net/ and saw the domain NS only resolving in 3 countries since 4 days.
=>There are a couple of possible reasons why your domain might not be working with AWS even though you've added the NS records:
=>Propagation Delay: It can take up to 48 hours for DNS changes to propagate globally. So, even though you added the records 4 days ago, it might still be working its way through the system.
=>Misconfiguration: Double-check that the NS records in your domain registrar exactly match the ones provided by AWS Route 53. A typo or any difference can prevent your domain from resolving correctly.
=>Here's a quick way to troubleshoot: Check Propagation: Use a tool like DNS Checker to see if the new NS records are showing up at different locations around the world.
=>Verify NS Records: Make sure the NS records in your domain registrar account match the ones in your AWS Route 53 hosted zone.
=>If you've verified these steps and it's still not working after a day or two, consider contacting AWS support for further assistance.
In a similar consultation the other day, there was no problem with the Route53 configuration, but we could not figure out why it was not reflected, so they responded with a workaround of creating a new Route53 host zone and switching to that.
https://repost.aws/questions/QULTShDRlnQW6hL361TRjMrw#ANRuSwF35KToOe6Lfi6xnaTg
Relevant content
- asked a year ago
