- Newest
- Most votes
- Most comments
You managed to resolve the issue, but for others finding this question, the solution is to update the name server configuration for the domain to those for the hosted zone: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html ("Adding or changing name servers or glue records").
When you transferred the domain name to Route53, did you choose the option to "Continue to use the name servers provided by the current registrar or DNS service" option? (See https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-to-route-53.html under Name Server Options). If yes, then the domain was transferred with the existing Name Servers in tact.
If that is the case, you will need to update the name servers for the domain manually in Route53 to the ones that are provided in the hosted zone. See: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing
Relevant content
- asked 6 months ago
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
I had to delete the DNSSEC from there I was able to update the NS under the Registered Domain information.