← All articles

Infrastructure

DNS — how a name becomes a server

2026-07-13 · 5 min read

Computers don't talk to names, they talk to numbers — IP addresses like 104.21.5.9. But you type codedrives.com, because nobody memorises numbers. DNS, the Domain Name System, is the internet's phone book: the system that turns a human name into the machine address your browser connects to. It happens before every page load, usually in milliseconds, and you never see it.

A relay race, not a lookup

There's no single giant list of every domain. Instead the answer is assembled by asking a hierarchy of servers, each of which knows only the next step. Your resolver (run by your ISP or a service like Cloudflare) does the legwork: it asks the root servers who handles .com, asks that TLD server who handles codedrives.com, and asks that authoritative server for the actual IP.

How a DNS query resolves Browser codedrives.com? Resolver does the legwork Root · who does .com? .com TLD · who does it? Authoritative · the IP 1 2 3 104.21.5.9 → back to the browser
The resolver walks down the hierarchy — root, then TLD, then authoritative — collecting one clue at a time until it has the IP.

Why it feels instant anyway

That whole relay sounds slow — several round trips before the page even starts loading. It isn't, because of caching. Every answer comes with a TTL, and resolvers (and your own machine, and your browser) remember it. The first person to look up a domain triggers the full walk; everyone after gets the cached answer in a fraction of a millisecond. It's the same caching trade-off as everywhere else — which is exactly why DNS changes "take time to propagate": the old answer is still cached somewhere until its TTL runs out.

The gist

DNS turns a name into an address by asking a chain of servers — root → .com → the domain's own server — each pointing to the next. Then everyone caches the answer, so it only happens the slow way once.

Where it fits

DNS is the very first step of loading any site — it runs before the connection, before the TLS handshake, before your reverse proxy ever sees the request. It's also the lever behind a lot of infrastructure: pointing your domain at a new server, splitting traffic across regions, or sitting a CDN in front of everything all come down to what your authoritative DNS returns. Quiet, constant, and load-bearing — the internet's address book, consulted before every knock on every door.


DNSInfrastructureNetworkingWeb
← Back to the blog