Explainer
How DNS works: resolvers, root servers and caching
The Domain Name System (DNS) is a distributed directory that organizes names as a tree and spreads the data across many name servers, each holding part of it.[1][2] Programs called resolvers find answers for users by asking name servers and following referrals, starting from the root zone, which IANA manages and which is served by 13 named root server authorities.[3][4][5] Answers are cached for a time set by each record, DNSSEC lets resolvers check that answers are authentic, and newer standards encrypt DNS traffic.[6][7][8]
This explainer covers how DNS lookups work and how the system is secured. Domain policy, registrars and the new top-level domain programme are covered on the ICANN page.
Names as a tree
Computers on the internet find each other by numeric addresses, but people use names. DNS is the directory that links the two.[3][9] It is not one big list: it is a tree of names whose branches are looked after by different servers around the world.[1][2]
The DNS name space is a tree in which each node has a label of up to 63 octets.[1] Name servers hold data about part of the tree, usually complete information about one subset (a zone) plus pointers to the servers for other parts, and they may cache data about the rest.[2] Resolvers are the client side: they extract information from name servers for client requests, answering directly or following referrals.[3]
At the top sits the root zone. IANA manages it and publishes the delegation details of every top-level domain, such as .com or a country code.[4] ICANN describes the root as a single file, copied to every root server, that lists where the address book for each top-level domain can be found.[10]
A lookup step by step
Suppose your browser needs the address for a name. It asks a resolver. If the answer is not already cached, the resolver works down the tree: the root servers point it to the servers for the top-level domain, which point it to the servers responsible for the name itself.[3][10]
The original specification describes two modes. In recursive mode the first server pursues the query on the client’s behalf; in iterative mode a server refers the client to another server and lets the client continue.[11]
Queries normally travel over UDP to port 53. In the 1987 specification, UDP answers were limited to 512 bytes, and longer answers were truncated and flagged.[12]
The root servers
The root zone is served by hundreds of servers in many countries, configured as 13 named authorities, a.root-servers.net through m.root-servers.net.[5] As of 7 November 2026 the root server system had 2,048 operational instances run by 12 independent operators.[13] The operators include Verisign, ICANN, NASA, the US Department of Defense, RIPE NCC and the WIDE Project.[5]
Caching and TTLs
Resolvers keep answers in a cache so they do not have to repeat the whole lookup every time. Each record carries a time-to-live (TTL) that limits how long it may be cached.[6] This is why a change to a website’s DNS records can take time to reach everyone: resolvers holding the old answer may keep using it until its TTL runs out.[6]
Securing DNS
The DNS Security Extensions (DNSSEC) add data origin authentication and data integrity, so a validating resolver can tell whether an answer really came from the zone’s owner, but DNSSEC does not hide the content of queries.[7]
For privacy the IETF standardized encrypted transports. DNS over TLS (2016) uses Transport Layer Security to remove opportunities for eavesdropping and on-path tampering, and DNS over HTTPS (2018) carries each query and response as an HTTP exchange.[8] For how DNS fits with addressing and routing, see how the internet works; for the bodies that coordinate names and numbers, see ICANN.
Read next
Next in the crash course
ICANN and IANA: who coordinates domain names and IP addresses
ICANN and IANA explained: who coordinates domain names, IP addresses and the DNS root, the 2016 IANA transition, and the 2026 new domain round.
Questions readers ask
What does DNS do?
DNS stores information about names in a tree-shaped name space spread across many name servers. Resolvers query those servers on behalf of users, for example to find the address behind a website's name.[1][2][3]
How many root servers are there?
The root zone is configured as 13 named authorities, a.root-servers.net to m.root-servers.net, but these are served by hundreds of servers worldwide. As of 7 November 2026 there were 2,048 operational root server instances run by 12 independent operators.[5][13]
Why do DNS changes take time to show up?
Every DNS record has a time-to-live (TTL) that limits how long resolvers may keep it in their cache. Until a cached copy expires, a resolver can keep giving out the old answer.[6]
What is DNSSEC?
The DNS Security Extensions add data origin authentication and data integrity to DNS, so a resolver can check that an answer is genuine. DNSSEC does not provide confidentiality.[7]
What are DNS over HTTPS and DNS over TLS?
They are IETF standards that encrypt DNS traffic. DNS over TLS (2016) aims to remove opportunities for eavesdropping and tampering; DNS over HTTPS (2018) carries each query and response as an HTTP exchange.[8]
Sources
· 13 claims from 4 publishers
Each numbered claim is a statement we checked against the sources listed with it. Tap a number in the text to see its sources in place.
- [1]
The Domain Name System organizes names as a tree; each node has a label of up to 63 characters (octets). confirmedas of 1987-11-01
- RFC 1034: Domain Names - Concepts and Facilities · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 3.1 (retrieved 2026-11-07)
- RFC 1034: Domain Names - Concepts and Facilities · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 3.1 (retrieved 2026-11-07)
- [2]
In DNS, name servers hold information about part of the domain tree, usually complete information about one subset plus pointers to other name servers, and they may cache information about other parts. confirmedas of 1987-11-01
- RFC 1034: Domain Names - Concepts and Facilities · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 2.4 (retrieved 2026-11-07)
- RFC 1034: Domain Names - Concepts and Facilities · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 2.4 (retrieved 2026-11-07)
- [3]
DNS resolvers are programs that get answers from name servers for clients, either answering from one server's data or following referrals to other name servers. confirmedas of 1987-11-01
- RFC 1034: Domain Names - Concepts and Facilities · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 2.4 (retrieved 2026-11-07)
- [4]
IANA manages the DNS root zone and publishes the delegation details of every top-level domain. confirmedas of 2026-11-07
- Root Zone Database · IANA · Primary source (retrieved 2026-11-07)
- [5]
The DNS root zone is served by hundreds of servers in many countries, configured as 13 named authorities (a.root-servers.net to m.root-servers.net) run by organizations including Verisign, ICANN, NASA, the US Department of Defense, RIPE NCC and the WIDE Project. confirmedas of 2026-11-07
- Root Servers · IANA · Primary source (retrieved 2026-11-07)
- Root Servers · IANA · Primary source · List of Root Servers table (retrieved 2026-11-07)
- Root Servers · IANA · Primary source · List of Root Servers table (retrieved 2026-11-07)
- Root Servers · IANA · Primary source · List of Root Servers table (retrieved 2026-11-07)
- Root Servers · IANA · Primary source · List of Root Servers table (retrieved 2026-11-07)
- Root Servers · IANA · Primary source · List of Root Servers table (retrieved 2026-11-07)
- Root Servers · IANA · Primary source · List of Root Servers table (retrieved 2026-11-07)
- Root Servers · IANA · Primary source · List of Root Servers table, e.root-servers.net (retrieved 2026-11-07)
- Root Servers · IANA · Primary source · List of Root Servers table, g.root-servers.net (retrieved 2026-11-07)
- [6]
Every DNS record carries a time-to-live (TTL) that limits how long it may be kept in a cache. confirmedas of 1987-11-01
- RFC 1034: Domain Names - Concepts and Facilities · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 3.6 (retrieved 2026-11-07)
- [7]
The DNS Security Extensions (DNSSEC) add data origin authentication and data integrity to DNS, but do not provide confidentiality. confirmedas of 2005-03-01
- RFC 4033: DNS Security Introduction and Requirements · IETF (RFC Editor) · Primary source · 2005-03-01 · Abstract (retrieved 2026-11-07)
- RFC 4033: DNS Security Introduction and Requirements · IETF (RFC Editor) · Primary source · 2005-03-01 · Section 4 (retrieved 2026-11-07)
- [8]
The IETF has standardized ways to encrypt DNS traffic, including DNS over TLS (2016), which it says removes opportunities for eavesdropping and on-path tampering, and DNS over HTTPS (2018), which maps each query and response into an HTTP exchange. confirmedas of 2018-10-01
- RFC 7858: Specification for DNS over Transport Layer Security (TLS) · IETF (RFC Editor) · Primary source · 2016-05-01 · Abstract (retrieved 2026-11-07)
- RFC 8484: DNS Queries over HTTPS (DoH) · IETF (RFC Editor) · Primary source · 2018-10-01 · Abstract (retrieved 2026-11-07)
- [9]
IPv4 was first deployed on 1 January 1983 and is still the most commonly used version of IP; its addresses are 32-bit numbers usually written as four numbers separated by dots. confirmedas of 2026-11-07
- Number Resources · IANA · Primary source (retrieved 2026-11-07)
- [10]
ICANN explains that all root servers store a copy of the same file, which lists where the address book for each top-level domain such as .com or .de can be found. confirmedas of 2026-11-07
- What Does ICANN Do? · ICANN · Primary source · What about root servers? (retrieved 2026-11-07)
- [11]
DNS supports two query modes; in recursive mode the first server pursues the query on the client's behalf, while in iterative mode the server refers the client to another server and lets the client continue. confirmedas of 1987-11-01
- RFC 1034: Domain Names - Concepts and Facilities · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 2.3 (retrieved 2026-11-07)
- [12]
DNS servers use port 53, and standard queries normally travel over UDP; in the original specification UDP messages were limited to 512 bytes, with longer answers truncated and flagged. confirmedas of 1987-11-01
- RFC 1035: Domain Names - Implementation and Specification · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 4.2.1 (retrieved 2026-11-07)
- RFC 1035: Domain Names - Implementation and Specification · IETF (RFC Editor) · Primary source · 1987-11-01 · Section 4.2.1 (retrieved 2026-11-07)
- [13]
As of 7 November 2026 the root server system had 2,048 operational instances run by 12 independent root server operators. confirmedas of 2026-11-07
- Root Server Technical Operations Association · Root Server Operators · Primary source · Home page counter, timestamp 2026-11-07T22:37:48Z (retrieved 2026-11-07)
Revision history (1)
- Page created.
Created Nov 7, 2026. Last reviewed by an editor on Nov 8, 2026. Next scheduled review: May 1, 2027.
Cite this page
"How DNS works: resolvers, root servers and caching." ContentLora, updated Nov 7, 2026. https://contentlora.com/explain/how-dns-works
Spotted an error? Suggest a correction or emailcorrections@contentlora.com.