Once there was a small village with a tiny post office by its gate. One morning a villager came clutching a letter to Ah-He, the young postman. On the envelope was only a name — “To the third Liu child, over on Far Mountain” — and no house number.

“I don’t know where he lives either,” said Ah-He, “but don’t go asking your way door to door. Give me the letter. I’ll go fetch the address for you and put nothing in your hand but the exact house number.”

So the whole errand fell on Ah-He alone. He ran first to the crossroads, to the oldest librarian in town. She remembered not a single house number, but she remembered something more useful: which broad district each family name belonged to. “The Lius?” She squinted and pointed east. “I don’t know which room the third child keeps, but I know who to ask — go to the Liu Family Grand Registry, out east.”

Ah-He hurried to the Grand Registry. Its clerk didn’t know the third child’s door either, but knew who to send him to next. “The Lius keep their own steward for their household. Go to him — that’s where you’ll get the real answer.”

At last Ah-He found the old Liu steward. The steward opened his household book and read it straight off: “Seventh house on Far Mountain, the one with the blue-grey tiled roof.” That, finally, was the true and final answer.

On the walk home Ah-He jotted it into the little notebook he carried: “Third Liu child = seventh house, Far Mountain,” and beside it a small note: “Good until dusk.” For the rest of the day, anyone asking after that same person got an instant answer — no second trip. Once dusk passed the note expired and he’d have to ask again. He even wrote down “no such person,” so the same empty name wouldn’t send him running twice.

— By now you’ve probably recognized it: this whole routine of “I don’t know, but I know who to ask,” being handed down level by level, the final house number given by whoever holds the book, and the answer kept on file for a while — that is DNS recursive resolution.

What it is. When you type a domain name, your machine has a name, not an address. A recursive resolver (usually run by your ISP or a public service like 8.8.8.8) takes on the whole errand of “asking the way” end to end. It asks a root name server first — the root gives no final answer, only which TLD name server (like .com) to try. The TLD points it to that domain’s authoritative name server, and only the authoritative server holds the real A/AAAA record (the IP address). This “root → TLD → authoritative” chain of delegation lets the world’s names be governed locally, with no single master ledger.

Why it matters. Re-running all three hops on every click would be expensive, so the resolver caches each answer for as long as its record’s TTL allows, expiring only then — and even a “no such domain” (NXDOMAIN) gets negative caching. Caching makes most lookups feel instant, and it also explains why a changed DNS record “takes a while to take effect”: the old answer is still sitting in someone’s notebook, not yet past dusk.

Metaphor mapping

• The name on the envelope (the third Liu child) → the domain name you want to reach
• The villager handing over the letter → the client that starts the query (stub resolver)
• Ah-He, who runs the whole errand himself → the recursive resolver
• The crossroads librarian (points the way, gives no house number) → the root name server
• The Grand Registry, sorted by family name → the TLD name server (like .com)
• The old Liu steward with his household book → the authoritative name server
• “Seventh house, blue-grey tiled roof” → the A/AAAA record (the IP address)
• The “I don’t know, but here’s who to ask” hand-offs → delegation (NS records / referrals)
• The notebook entry marked “good until dusk” → a cache with a TTL
• Writing down even “no such person” → negative caching (NXDOMAIN)