- Newest
- Most votes
- Most comments
In addition to the previous answer, it is crucial to ensure that your Domain Registration settings are synchronized with your Hosted Zone. Finding the name servers in the Hosted Zone is only the first half. You must then:
-
Go to 'Registered domains' in the Route 53 console.
-
Select your domain and choose 'Add or edit name servers'.
-
Replace the existing servers with the four specific name servers found in your Hosted Zone.
Without this step, the domain will remain inactive because the registrar isn't 'pointing' to your DNS records yet. Note that DNS propagation can take a few hours to update globally.
When you have a domain registered with Route 53, you need to create a hosted zone for that domain to manage its DNS records. Each hosted zone gets its own unique set of four name servers automatically assigned by Route 53.
To find the correct name servers for your domain:
- Sign in to the AWS Management Console and open the Route 53 console
- In the navigation pane, click on "Hosted zones"
- If you don't already have a hosted zone for your domain, you'll need to create one with the same name as your domain
- Once you have the hosted zone, select it (choose the radio button, not the name) and choose "View details"
- On the details page, choose "Hosted zone details"
- Make note of the four servers listed under "Name servers"
These four name servers are unique to your hosted zone and are what you should use for your domain registration. You're correct that you cannot copy name servers from one domain to another - each hosted zone has its own dedicated set.
After you have your hosted zone set up with the appropriate records (such as your redirect configuration), update your domain registration to use these four name servers. Once the name servers are updated and DNS propagation is complete, your domain will be active again and Route 53 will handle all DNS queries for it.
The reason each domain has different name servers is by design - Route 53 automatically assigns a unique set of name servers to each hosted zone to distribute the DNS query load across its infrastructure.
Sources
Making Route 53 the DNS service for an inactive domain - Amazon Route 53
NS and SOA records that Amazon Route 53 creates for a public hosted zone - Amazon Route 53
Relevant content
- asked 4 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
Thank you for that clarification, I was doing the first bit of creating the hosted zone, but then wasn't copying over the the specific DNS' to the domain and thus they were out of sync.