When you create a hosted zone, Route 53 assigns four unique name servers to that hosted zone. When you create another hosted zone, Route 53 assigns four unique name servers to that hosted zone. Route 53 doesn't pay any attention to the name servers that are assigned to a domain registration when you create another hosted zone.
To make your domain work again, perform the following procedures:
- Get the name servers that are assigned to your hosted zone. See "Getting the Name Servers for a Public Hosted Zone" in the Route 53 Developer Guide:
- Update the domain registration to use the name servers that you got in step 1. See "Adding or Changing Name Servers and Glue Records for a Domain":
As simple as that... :)
Thanks Scott, all working now.
How to allign the Name Servers of Route53 Public Hosted Zone and Registered Domains in CDK?asked a year ago
Route 53 and External Domain registrar A record questionasked 2 years ago
Static website hosted in S3 using Cloudfront and Route 53 is downAccepted Answerasked a year ago
Hosted zone not configured properly for workmailasked a year ago
Incorrect NS record returned for domain after re-creating hosted zoneAccepted Answerasked 4 years ago
Route53 public hosted zone not resolving for my domainasked 6 months ago
I have moved my domain to another account, I have created the hosted zone but it does not forward to my ec2 instance and not to my load balancerasked a month ago
Why doesn't my hosted zone A record resolve correctly for an .io domain?Accepted Answerasked 4 months ago
No nameservers returned for my domainAccepted Answerasked 4 years ago
NS record type disabledAccepted Answerasked 9 months ago