Opscraft
Name servers & SOA · Lesson 5 of 8 · 4 min read

Route 53 name servers and registrars

Four name servers per hosted zone

Creating a public hosted zone gives you an NS record set with four name servers and an SOA:

ns-1234.awsdns-12.org.
ns-567.awsdns-07.net.
ns-89.awsdns-11.com.
ns-2001.awsdns-50.co.uk.

They're deliberately spread across four different TLDs (.com, .net, .org, .co.uk) — so a problem with one TLD's infrastructure can't make your zone unreachable — and they're anycast across AWS's global edge network. Route 53 offers a 100% availability SLA for its DNS service.

Enlarge diagramns-1234.awsdns-12.orgserved under .orgns-567.awsdns-07.netserved under .netns-89.awsdns-11.comserved under .comns-2001.awsdns-50.co.ukserved under .co.ukRecreate the hosted zone and you get four new servers: update the registrar, or the domain stops resolving.
Figure 1. Every Route 53 hosted zone gets four name servers in four different top-level domains, so a problem in one TLD cannot take your domain offline.
Swipe sideways to see all of it, or tap to open it full screen.

Facts to know:

  • Each hosted zone gets its own assignment of four servers; deleting and recreating a zone gives you new name servers — you must update the registrar again (a common outage when someone "recreates the zone in Terraform").
  • Reusable delegation sets let you use the same four name servers for many hosted zones (created via API/CLI), simplifying registrar updates and enabling white-label name servers (ns1.example.com pointing at Route 53 IPs, with glue).
  • You can't delete the apex NS and SOA records of a hosted zone.
  • Route 53 manages the SOA serial for you.

Connecting the registrar

  • Domain registered in Route 53 Domains: registering automatically creates a hosted zone and sets matching NS. If you recreate the zone, update the domain's name servers in Route 53 Domains.
  • Domain registered elsewhere (GoDaddy, Namecheap, an .in registrar): create the hosted zone in Route 53, then change the name servers at the external registrar to the four Route 53 servers.

Verify what the world sees:

dig NS example.com +short                         # what resolvers currently return
dig NS example.com @a.gtld-servers.net +norecurse # what the .com parent delegates to
whois example.com | grep -i "name server"         # registrar's view

If the parent's NS (from the TLD) differ from the hosted zone's NS, the internet uses the parent's — your hosted zone isn't being used.

Delegating subdomains across accounts

The standard multi-account pattern:

  1. In the dev account, create a public hosted zone dev.example.com → note its four NS.
  2. In the account owning example.com, create an NS record dev.example.com with those four values (TTL e.g. 172800, or lower during setup).
  3. Teams manage dev.example.com with their own IAM permissions; the parent zone stays locked down.

This is also how you give two teams independent control of records in one domain — delegate subdomains to separate hosted zones.

A newly delegated subdomain may take time to work if resolvers cached NXDOMAIN for it (negative TTL) or old NS data.

Private and public zones with the same name

You can have a public example.com zone and a private example.com (or internal.example.com) zone. Inside an associated VPC, the Route 53 Resolver answers from the private zone (falling back is not automatic — a name missing in the private zone returns NXDOMAIN even if it exists publicly, so replicate needed public records). Outside, the public name servers answer.