Names, Not Numbers

Quick test: what's the IP address of your favorite website? You have no idea — and that's correct. Humans are catastrophic at remembering numbers and excellent at remembering names. The internet knows this about us, so it runs a translation service between our names and its numbers, and you have used it several times already today without feeling a thing.

Domain names

The names are domain names — example.com and its billions of cousins. A domain name has structure, and the trick to seeing it is reading right to left, like the envelope of an old-fashioned letter that starts with the country:

learn.example.com

Rightmost, com — the broadest zone, one of the big top-level endings (org, net, country codes like .et). Then example — the specific name someone registered within com; that registration is what makes the name theirs, worldwide. Leftmost, learn — a sub-name its owner carved out freely, the way a building's owner names its own wings. Broad to specific, right to left: country, building, wing.

DNS: the phone book lookup

Names are for humans; the parcels of Unit 1 still demand numeric addresses on their labels. So before your phone can request anything from example.com, it must translate the name into an address. That translation service is DNS (the Domain Name System), and the step is beautifully mundane: look it up, then dial.

The moment you hit Enter, your phone asks a DNS server — remember the front desk's key folder including "who to ask about names"? this is that bookmark — "what address is example.com?" The answer comes back — 203.0.113.7 — and only then does the real request depart, parcels labeled with the number. Every site you visit, every app that phones home: name in, address out, then dial. Billions of lookups an hour, worldwide.

Two refinements make this bearable at scale. First, no single phone book holds the internet: DNS is a relay of servers, sorted the same right-to-left way the name reads — one layer knows who manages com, which knows who manages example.com, which knows the wing. Your one question hops down that chain and comes back answered in tens of milliseconds. Second, answers get remembered: your phone and your router keep recent lookups for a while, so the second visit skips the phone book entirely. (Keeping a copy you'll likely need again — hold that thought; Unit 3 makes a whole lesson of it.)

The payoff for your troubleshooting kit is a distinction: two failures that feel identical but say opposite things. A "site can't be found" style error means the lookup failed — the phone book had no listing (typo in the name, or DNS trouble). A "can't connect / took too long" error means the lookup worked and the number is known, but nobody answers the door. One is a missing listing; the other, a dark house. Knowing which you're looking at halves the mystery instantly.

Names resolve, addresses label, parcels fly. One more piece and the map is complete: your laptop is streaming, chatting, and downloading at the same time — one address, many simultaneous conversations, and not a parcel misdelivered between them. How? Numbered doors. Next lesson: ports.