Route 53 Hosted Zone records not propagating

Question

Hi,
I have a fairly simple setup, yet I continue to get a `ERR_NAME_NOT_RESOLVED ` error.

I have a domain and corresponding hosted zone in Route 53. I added an `A`, `AAAA`, and `CNAME` record for a fly.io resource. The `A` and `AAAA` records point to their respective ip4 and ip6 addresses. The `CNAME` record is simply for fly.io to verify domain ownership. I've tried without the `CNAME` record but get the same results. All the record's routing policies are simple. Is there a way to debug this? As far as I can tell, the hosted zone is active and should be publicly available.

The only other listed records are the `NS` and `SOA` which point to AWS resources.

I've also asked this question with the fly.io community: https://community.fly.io/t/host-fly-node-server-on-route-53-subdomain/10581/5

Following the advice of [this post](https://repost.aws/questions/QUIqznlupsQ8m2RCrIvoQxyg/route-53-hosted-zone-not-forwarding#ANV43AwBKYSJmZQFzSF_NhUA), I also confirmed the values of the NS record in my hosted zone match that of my domain

Accepted Answer

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

Answer

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.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html#migrate-dns-change-name-servers-with-provider

Route 53 Hosted Zone records not propagating

相关内容