DNS, the Internet's Phonebook

You type example.com and press Enter. But the last topic showed that computers don't find each other by name — they find each other by number, the IP address. So something has to step in between the name you typed and the number the network needs, and do it before the page can even begin to load.

That something is DNS — the Domain Name System — the service that turns the names you type into the numeric addresses computers use. It runs silently before almost everything you do online, and most people never know it's there until the moment it stops working.

You type a nameexample.com

→

Ask DNSname? → address

→

Connect to the address93.184.x.x

What does DNS actually do?

DNS does one thing: it looks up the numeric address for a name. You give it example.com; it gives you back the IP address of the computer that serves that site — a number like 93.184.x.x. That single lookup is the whole job.

It's worth being precise about what DNS does not do, because the name "Domain Name System" makes it sound bigger than it is. DNS never sends you the web page, the images, or any of the site's content. It answers exactly one question — "what is the address for this name?" — and then your computer takes that address and goes to fetch the page on its own.

The phonebook idea

Think of an old phone directory. You know a person's name but not their number, so you look the name up and the book gives you the number to dial. DNS is that directory for the internet: you know the name, DNS gives you the address, and then your computer "dials" it by connecting.

The analogy holds in one more useful way and then breaks in a telling one. Like a phonebook, DNS only ever hands you a number to reach someone — it is not the person, just the listing. But unlike a single printed book, there is no one giant DNS directory sitting in one place.

Instead, DNS is distributed — spread across a huge number of cooperating computers around the world, each responsible for part of the directory. No single machine holds every name. When your computer asks for an address, the question may pass through several of these servers until it reaches the one that knows the answer for that particular name.

The lookup, step by step

Here is the sequence, in order. Your computer has a name and needs an address. It sends that name to DNS and asks for the matching IP address. DNS finds it and sends the number back. Only now, holding the address, does your computer open a connection to that machine and ask it for the actual page.

All of this usually finishes in a fraction of a second, before you notice any delay. And because the same names come up again and again, your computer keeps recent answers nearby for a while — a saved copy it can reuse — so it doesn't have to ask DNS from scratch every single time you visit a site you were just on.

Why DNS can be slow or fail

Because the DNS lookup happens before anything else, it sits on the critical path: if it's slow, the whole page feels slow, even when the website itself is fast. And if DNS can't find the address at all, your browser shows an error and the site simply won't load — not because the site is down, but because your computer never learned where to go.

This is why engineers have a running joke: "it's always DNS." When something on the internet breaks for no obvious reason, the cause turns out, with surprising regularity, to be a DNS problem — a wrong or missing entry in that distributed directory. It's a joke precisely because it's so often true.