DNS turns human-readable names into resource records. A client typically asks a recursive resolver, and that resolver uses cached data or follows the DNS hierarchy: root servers point toward the appropriate TLD servers, which point toward authoritative servers for the domain. The final answer is cached according to TTL.
Remember the shape, not the sentence
“Think of a chain of increasingly specialized librarians. The first librarian either knows the answer or asks the next librarian, keeping a copy so future students do not repeat the whole search.”
Recursive vs authoritative
A recursive resolver performs the work of finding an answer on behalf of the client. An authoritative server stores zone data and answers authoritatively for domains it serves.
Records are typed
A records map names to IPv4 addresses, AAAA records to IPv6 addresses, CNAME introduces an alias, MX points to mail exchangers, and TXT carries arbitrary text used for several policy and verification purposes.
Caching is central
Resolvers cache answers for their TTL. This reduces load and latency but means changes do not necessarily appear everywhere instantly.
See the mechanism before you memorize it
One diagram, one causal story, one reconstruction task.
DNS end-to-end: resolver → root → TLD → authoritative — causal map
Client
Ask the configured resolver for a record.
Cache
Resolver checks its own cached answer first.
Root
If needed, discover which TLD servers know about the domain.
TLD
Discover the authoritative server for the domain.
Draw the idea yourself
Rebuild the core flow on a real canvas before moving to the worked walkthrough.
Walk the system
Client
Ask the configured resolver for a record.
Cache
Resolver checks its own cached answer first.
Root
If needed, discover which TLD servers know about the domain.
TLD
Discover the authoritative server for the domain.
Authoritative
Return the zone's record; resolver caches and returns it to the client.
Inspect DNS
The normal query shows what your resolver returns. +trace illustrates the hierarchy by following referrals more directly.
dig example.com A
dig example.com AAAA
dig example.com MX
dig +trace example.comWhat usually goes wrong
Close the tab. Rebuild it from memory.
Read the question, answer aloud, then reveal.
What is recursive resolution?Reveal answer
The resolver performs the sequence of queries needed to obtain the final answer on behalf of the client.
Why does TTL matter?Reveal answer
It controls how long a cached answer may be reused before the resolver should refresh it.
What is authoritative about an answer?Reveal answer
It originates from the zone's authoritative servers rather than from an intermediate cache.
Make this idea travel.
Connect it next to: dns-journey • http-versions • devtools.