1 Answer
- Newest
- Most votes
- Most comments
1
Does the GLUE record for your domain point to the Route53 name servers or old NS Servers? If not, they will need updating.
You can find the NS records for your domain in route53 and ensure you update the DNS Records via your registrar https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
Relevant content
- Accepted Answerasked 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
I ran the command aws route53domains get-domain-detail --region us-east-1 --domain-name <my-domain>.com and got back the expected aws name servers. It also shows there are no Glue IPs.
The NS record in the hosted zone doesn't show the same name servers as the registered domains page in the console, but I've been told that is normal and to keep what the hosted zone generates. Do you think the issue is something related to it being a transferred domain? AWS is my registrar and I have tried changing the name servers to match the hosted zone, but I they end up failing when I change away from the original values. My DNS lookup tests say there are no NS records for my domain
No that’s not normal! You said you recreated the route53 zone. Because you did you have ended up with different name servers. You have to update the glue records to match the name servers in the route53 zone
When you carry out a whois lookup for your domain is the registrar aws and then name severs match the ones in your zone?
Thanks so much! I got it to work. Didn't realize you have to use the same name servers under the registrar and the NS records
Your welcome. Yeah this is how dns works on the internet. Glad it’s resolved.