Opscraft
How DNS works behind the scenes · Lesson 3 of 9 · 3 min read

Root servers, TLDs and the governance behind them

Root servers

  • There are 13 root server identities, a through m (a.root-servers.net … m.root-servers.net) — a limit from the original 512-byte UDP response size.
  • They're operated by 12 independent organisations (Verisign runs both A and J; others include ICANN, NASA, the US Army, RIPE NCC, WIDE, ISC, University of Maryland, Cogent, Netnod, USC-ISI, US DoD).
  • Each identity is served by many anycast instances worldwide — over 1,800 sites in total, including several in India. Anycast means the same IP is announced from many locations and routing delivers your query to the nearest one, giving both speed and DDoS resilience.
  • Root servers only know the TLD delegations — they never know about example.com itself.

TLDs, registries and registrars

  • IANA (operated by ICANN) manages the root zone contents — which TLDs exist and their name servers; Verisign handles root zone publishing.
  • Generic TLDs (.com, .net, .org, .dev) and country-code TLDs (.in, .uk, .de — .io is technically a ccTLD too).
  • A registry operates a TLD's database and name servers (Verisign for .com; NIXI for .in).
  • A registrar (Route 53 Domains, GoDaddy, Namecheap...) sells domains and submits your name servers (and DS records for DNSSEC) to the registry.
Enlarge diagramYoubuyexample.comRegistrarRoute 53Domains,GoDaddy…RegistryVerisign for.com, NIXI for.inTLD serversnow point toyour nameserversNS (and DS)publishes
Figure 1. Who does what when you buy a domain. You set your name servers at the registrar; the registry publishes them in the TLD.
Swipe sideways to see all of it, or tap to open it full screen.