- Newest
- Most votes
- Most comments
- Open your Route53 Public Zone in Route53
- Take a note of the 4 NS Server Records
- Following these instructions, remove ALL existing NS records from your Domain https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing
- Add the 4 NS Servers from Step 2
Ensure that you adhered to the proper DNS domain name format when setting up your records.
Thanks for your answer Osvaldo. Yes it is. The domain only use letter of the English alphabet (6 letters) and end in ".com".
Update the domain glue records to point to the name servers in your route53 zone.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
Hi Gary, I have not touched or edited the records that AWS automatically adjusts. I just add two. Thanks for your reply.
Did that fix your problem?
Be sure to have the 4 from your zone and remove the others.
I don't touch the one that AWS set from the beginning (NS and SOA) and I add the A one and the CNAME. But still can't resolve my domain thru browser.
Make sure you enter all 4 NS records as the glue records and delete anything hint AWS set on your domain.
Relevant content
- asked 4 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
Great, it work strait away. Now I'm getting a 404 error but from the domain side, it's working. Curious that AWS set different NS for the domain and for a hosted zones. Lesson learned! Thanks!!