- Newest
- Most votes
- Most comments
Ensure that the nameservers associated with your domain are correctly configured and pointing to the correct Route 53 hosted zone in your new AWS account.
aws route53 list-hosted-zones-by-name --dns-name mydomain.com
After transferring the domain, you need to update the nameserver delegation at the domain registrar (which is now AWS) to point to the correct Route 53 nameservers.
aws route53 get-hosted-zone --id <hosted-zone-id>
Verify the nameservers listed in the output and ensure they match the nameservers listed in the domain's registration settings.
DNS changes can take time to propagate. Ensure you've allowed sufficient time for the changes to take effect (usually up to 48 hours).
Ensure that the zone file (DNS records) in the Route 53 hosted zone contains the necessary records (A, AAAA, CNAME, etc.) for your domain.
If the issue persists, consider reaching out to AWS Support for further assistance.
Thanks for the info. Do you happen to know if there is a way to do this through the console or only with cli and set up a user with permissions, etc?
answered 2 years ago
So I have other domains which I transferred from another registrar and the nameservers listed on the domains match the nameservers of the associated hosted zones. But this one domain which I transferred from one AWS account to another, the nameservers listed on the domain do not match the ones of the hosted zone. It makes no sense that an internal transfer would have issues. Not sure what to do here. :(
answered 2 years ago
Nevermind, I thought I could change the hosted zone nameservers but can't and realized that I needed to change the domain nameservers instead.
answered 2 years ago
