DNS

You don't remember a single phone number anymore. You tap a name and your phone fills in the ten digits behind it. DNS does that exact job for the entire internet.

Here's the thing computers won't tell you to your face: they don't actually know what google.com is. Names mean nothing to them. Every machine that serves a website lives at a numeric address called an IP address, something like 142.250.80.46. That's the real location. The name is just a sticker we slapped on top so humans don't have to memorize a phone book full of numbers.

So every time you type a web address and hit enter, a quick lookup happens before anything loads:

1. You type google.com.

2. Your browser turns to DNS and asks, "what's the actual number behind this name?"

3. DNS hands back the IP address.

4. Now your browser knows where to go, and it goes there.

That whole round trip happens in the blink before the page even starts loading. You never see it. It's the contacts app of the internet, running quietly under every single thing you do online.

Where you've felt this without knowing what it was.

Ever buy a domain and the seller says "give it up to 48 hours to start working"? That wait is DNS. You bought the name, but the world's phone books haven't all gotten the update yet. The new entry has to spread from one phone book to the next, all over the planet, before everyone's looking at the same number. That spreading has a name (propagation), and it's why a brand-new site sometimes loads for you and not for your friend across the country. Your phone book got the memo. Theirs didn't yet.

Why this matters the second you put anything online.

Owning a domain is two separate things people constantly mash together:

• Buying the name. You own mycoolsite.com. It's yours. Nobody else can have it.
• Pointing the name. Telling DNS which machine that name should send people to.

Buying it does nothing on its own. It's a contact saved with no number attached. The pointing is the part that makes it actually go somewhere. So when you set up a site and the host says "add these DNS records," they're handing you the number to write down next to your contact. You're filling in the phone book entry for your own name.

A couple of the entries you'll bump into, in plain English:

• An A record points a name straight at an IP address. "google.com lives at this number." The basic one.
• A CNAME points one name at another name instead of a number. "treat www.mysite.com the same as mysite.com." A nickname that forwards to the real contact.

You don't need to memorize these. You just need to not panic when a setup screen asks for them. It's a form asking which number goes with which name.

The line you'll actually hear. When something breaks and someone shrugs and says "it's probably a DNS issue," there's a famous joke engineers tell: it's always DNS. Translated: the site itself is fine, the machine is up and cooking, but the name is pointing at the wrong place (or hasn't finished spreading), so nobody can find the front door. The restaurant's open. The address on the sign is just wrong, so everyone's circling the block.

The machine has a number. You have a name. DNS is the translator standing in the middle, and almost nothing online would work without it.