2 Answers
- Newest
- Most votes
- Most comments
1
As @jason eluded to, the issue was with the name servers. My hosted zone and domain had different name server values. I update the domain to match those of the hosted zone, and then updated the ns records within said hosted zone to also match. More information here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/troubleshooting-new-dns-settings-not-in-effect.html#troubleshooting-new-dns-settings-not-in-effect-recent-transfer-wrong-name-servers
answered 2 months ago
0
Who is the registrar for the domain you are creating records for? If Route53 isn't the registrar of the domain, you need to set the NS records on the domain registrar site to point to Route 53's servers.
answered 2 months ago
Relevant content
- asked 7 months ago
- asked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Amazon is. I just did a sanity checked and can verify the NS records listed on an ICANN lookup match those that are assigned to the domain (and the hosted zone as well).
blakenetzeband.com
on https://lookup.icann.org/en/lookup