- Newest
- Most votes
- Most comments
Based on the information provided, it appears that your DNS configuration in Route 53 is correct, but there might be an issue with the nameserver (NS) records for your domain. Here are some potential reasons and solutions for your situation:
- Nameserver Mismatch: The most likely cause of your issue is a mismatch between the nameservers listed in your domain registration and those in your Route 53 hosted zone. When you register a domain with Route 53, it automatically creates a hosted zone with the correct nameservers. However, if you've created a new hosted zone manually, the nameservers may not match.
To resolve this:
- Go to the Route 53 console and check the nameservers listed in your hosted zone for getalmayor.com.
- Then, go to the Registered Domains section in Route 53 and verify that the nameservers listed for your domain exactly match those in the hosted zone.
- If there's a mismatch, update the nameservers in the domain registration to match those in the hosted zone.
-
Glue Records: Ensure that the glue records for your domain are correctly set. These are critical for proper DNS resolution.
-
TTL Values: Check the Time-to-Live (TTL) values on your DNS records. While you've waited more than 48 hours, some resolvers might cache information for longer periods.
-
Multiple Hosted Zones: If you have multiple hosted zones with the same name, ensure you're updating the correct one and that the domain registration is using the correct nameservers.
To further troubleshoot:
- Use online DNS lookup tools that allow you to specify the nameserver, and check if they return the correct IP address when querying your AWS nameservers directly.
- Verify that your domain registration details are correct and that you've confirmed any necessary verification emails from ICANN.
If you've verified all these points and are still experiencing issues, it may be worth considering an upgrade to a support plan that allows direct contact with AWS Support, as they can provide more in-depth assistance with domain and DNS configuration issues.
Sources
Domain Registration Successful but Unable to Resolve Domain | AWS re:Post
I changed DNS settings, but they haven't taken effect - Amazon Route 53
Migrated domain to AWS and DNS not working in many places | AWS re:Post
Solved with AWS agent support. The NS from the registered domain should be re created and then, update the hosted zone. The agent provide me new Name Servers. I am not sure where they come from, but now the dns is propagating.
Hello.
If you check the "whois" command, you can check the following NS records.
Will name resolution fail even if I change to the NS record below?
whois getalmayor.com
Name Server: NS-1408.AWSDNS-48.ORG
Name Server: NS-16.AWSDNS-02.COM
Name Server: NS-1642.AWSDNS-13.CO.UK
Name Server: NS-773.AWSDNS-32.NET
The NS records provided by the command whois getalmayor.com are the same that are showed in the picture that I shared in my last response wich is the current NS record in AWS hosted zone, so I don't understand what is your point. Would you give me more details about your question?
Okey, so there was a mismatch, so I copied the NS from the details showed in registered domain in the NS register of the hosted zone.
Reading the data in the links that are provided in the automatic answer, I have to wait 2 days in to get some propagation.
Hello. 2 days have past, and there is no propagation of the dns. What should I do?
Relevant content
- asked 10 months ago
- asked 8 days ago
- asked 8 months ago
- asked 7 months ago
You are much more patient than I. I have a situation similar to yours - though I haven't done all the detective work you have. How do you get AWS agent support? I can't find a way to contact anyone... thank you!