The Question That Traveled the World
A DNS Resolution Journey
The Human Moment
Sara types eleven characters into her browser's address bar:
stripe.com
She presses Enter.
From Sara's perspective, she's simply asking for a webpage. But her browser sees a different problem entirely. "stripe.com" is just a name — a human-readable label. Names are for humans. To actually connect to Stripe's servers, the browser needs a number: an IP address.
The browser doesn't know what number belongs to "stripe.com."
So begins the search.
The Cache Gauntlet
Before any network traffic occurs, the question must pass through layers of memory. Each layer might already know the answer — and if it does, the journey ends early.
The browser checks its own memory first. Has anyone asked for "stripe.com" recently?
Browser Cache Lookup
"stripe.com" → ?
MISS — Not in browser cache
Nothing. Either Sara has never visited Stripe on this browser, or the cached answer has expired. The browser passes the question to the operating system.
The OS first checks the hosts file — an ancient mechanism that lets a computer override DNS entirely. If someone has manually written "stripe.com = 1.2.3.4" in this file, that answer wins.
Hosts File Check
/etc/hosts → "stripe.com" → ?
NO ENTRY — Not in hosts file
No manual override exists. The OS checks its own DNS cache — other applications might have asked for "stripe.com" recently.
OS DNS Cache Lookup
"stripe.com" → ?
MISS — Not in OS cache
All local caches are empty. The question must leave this computer and travel across the network.
Mac/Linux: /etc/hosts
This file predates DNS itself. It was how the early internet worked — everyone maintained a list of all computers!
A Query Is Born
The operating system hands the question to its stub resolver — a small piece of software whose only job is to forward DNS questions to a real DNS server and wait for answers.
The stub resolver builds a DNS query packet. This is Query-7741 — our protagonist.
DNS Query Packet — 42 bytes
The query is wrapped in a UDP datagram, destination port 53 — the standard DNS port. The stub resolver sends it to the configured DNS server: 8.8.8.8 (Google Public DNS).
Query-7741 leaves Sara's laptop. It crosses her home network, passes through her router, enters her ISP's network, and travels across the internet to Google's DNS infrastructure.
The Recursive Resolver
Query-7741 arrives at Google's recursive resolver — a powerful server whose job is to answer DNS questions on behalf of clients. The resolver is the workhorse of DNS resolution.
Recursive Resolver
The Detective — Does the legwork to find answers
The resolver checks its own massive cache. Millions of users have asked questions recently — maybe someone already asked about stripe.com?
Resolver Cache Lookup
"stripe.com" → ?
MISS — Not in resolver cache
No luck. The resolver must find the answer the hard way — by asking the DNS hierarchy directly. This is where the "recursive" in "recursive resolver" comes from: it will recursively query other servers until it finds the answer.
The resolver begins at the very top of the DNS hierarchy: the root servers.
The Root of All Names
The resolver sends a query to one of the 13 root server addresses. These aren't 13 individual machines — each address is actually served by hundreds of servers distributed worldwide using anycast routing.
Root Server (a.root-servers.net)
The Librarian — Knows who manages each top-level domain
The root server doesn't know stripe.com's IP address — and it never will. Root servers only know one thing: who manages each top-level domain (TLD). They're like a librarian who doesn't know every book, but knows which section each book belongs to.
Root Server Response — Referral
The root server provides a referral — not an answer, but a pointer to servers that might know more. The resolver follows this lead.
The TLD Server
The resolver now queries a .com TLD server — operated by Verisign, which manages the entire .com registry containing over 150 million domain names.
.COM TLD Server (a.gtld-servers.net)
The Registrar — Knows who owns each .com domain
The TLD server knows about stripe.com — but still doesn't know its IP address. It only knows which nameservers are authoritative for that domain. These nameservers are designated by Stripe when they registered their domain.
TLD Server Response — Referral
Notice the "glue records" — these are IP addresses included with the referral. Without them, we'd have a chicken-and-egg problem: how do you find ns1.stripe.com if you need to ask ns1.stripe.com?
Country Code TLDs: .uk, .de, .jp, .in
New TLDs: .app, .dev, .io, .xyz
Each TLD has its own set of servers managed by different organizations.
The Authoritative Server
The resolver reaches the final destination: Stripe's own authoritative nameserver. This server has the actual answer — the IP address that Sara's browser needs.
ns1.stripe.com (Authoritative)
The Source of Truth — Knows exactly where stripe.com lives
Finally! The authoritative server responds with an actual answer — not a referral, but the IP address itself.
Authoritative Response — THE ANSWER
The Return Journey
The resolver now has the answer. Before sending it back to Sara's computer, it caches the result — and every other piece of information it learned along the way.
The resolver sends the answer back to Sara's computer. The stub resolver receives it, and the OS caches it. The browser receives it, and the browser caches it too.
Query-7741's mission is complete. Total time elapsed: 63 milliseconds.
The Power of Memory
Sara visits stripe.com again. This time, the journey is very different.
Browser Cache Lookup
"stripe.com" → ?
HIT — 192.0.2.50 (TTL: 237s remaining)
The browser finds the answer in its own cache. No network traffic required. No DNS servers contacted. The answer arrives in under 1 millisecond.
This is why DNS caching exists. The full resolution took 63 milliseconds and required queries to four different servers. The cached lookup took less than a millisecond and required zero network traffic.
Now imagine this multiplied by billions of DNS queries per day, across millions of users. Caching isn't just an optimization — it's what makes DNS scale to internet size.
The Connection
With the IP address in hand, Sara's browser can finally do what it wanted to do all along: establish a TCP connection to Stripe's servers and request the webpage.
The DNS resolution that just occurred — Query-7741's entire journey — happened in the space between Sara pressing Enter and the first pixel appearing on her screen. She never saw it. She never knew about it.
But without it, the modern internet wouldn't work.
Every website you visit, every app that connects to the cloud, every email you send — all of them begin with a DNS query. A question that travels the world, bouncing between servers, following the hierarchy from root to TLD to authoritative, until it finds the number that matches a name.