Names versus Numbers

You type example.com into your browser and the right page comes back. But an earlier chapter showed that computers don't find each other by name — they find each other by a numeric address called an IP address, a string of numbers like 192.0.2.10. So there's a gap: you typed a name, the computer needs a number. Something has to bridge that gap, automatically, every single time.

That bridge is a lookup — a translation that takes the name you typed and hands back the matching number. This topic is about why that translation has to exist at all; the next one names the system that does it.

example.comthe name

→

Lookuptranslate

→

192.0.2.10the number

Why Two Different Kinds of Address?

People and computers are good at different things. You remember example.com easily, the way you remember a friend's name. A computer remembers nothing the way you do — it works with numbers, and it routes traffic across the network using the numeric IP address each machine has.

So the internet ended up with two parallel systems for the same destination. There's the name, which exists for your benefit, and the number, which exists for the network's benefit. Both point at the same computer; they're just written in two different alphabets.

If there were only numbers, you'd have to type 192.0.2.10 to reach a site, and memorize a fresh string of digits for every place you wanted to visit. If there were only names, the network would have nothing concrete to route toward. Keeping both, and translating between them, lets each side use what it's good at.

The Lookup: Turning a Name into a Number

Because the two systems exist side by side, every visit needs a moment of translation. Before your browser can connect to example.com, it has to find out which number that name stands for. It asks the question "what is the address for this name?" and gets a number back.

Only then does the real connection begin. Armed with the number, your computer routes its request to that exact machine, using everything from the earlier chapters — packets, addresses, ISPs, the hop-by-hop journey across the world. The lookup is the quiet first step that makes all of that possible.

Your saved contacts work the same way. You tap "Mom" and the phone places the call — you never thought about her actual number. The contact list quietly held the digits and dialed them for you. The name is for you to remember; the number is what the phone network needs; and a lookup in between connects the two. The internet does exactly this, for every website, billions of times a day.

When Does the Translation Happen?

You never see this step, which is why it's easy to forget it exists. It happens automatically, in a fraction of a second, the instant you press Enter — before the page starts loading, before anything appears on screen.

It runs every time, not just the first. Each time you open a site, the same name-to-number translation happens behind the scenes, and the result is usually remembered briefly so a repeat visit can skip the question. You experience none of it: you type a name, and the page arrives. The translation is doing its job precisely when you don't notice it.

This whole translation system has a name — DNS, the Domain Name System — and it's the subject of the next topic. For now the point is narrower: names and numbers are two separate things, and a lookup connects them every time you open a website.