You don’t remember phone numbers anymore. You tap a name in your contacts. Turns out, the internet doesn’t remember numbers either. That’s the whole job of DNS.
Perfect for sending to someone who won't read a whole article.
Quick: what’s your best friend’s phone number? If you had to stop and think, you’re completely normal. Nobody memorizes numbers anymore. You tap their name in your contacts, and your phone finds the number for you.
(Old enough to remember phonebooks? Same idea. Just heavier, one per city, and not nearly as good at autocorrect.)
The internet works exactly the same way, and DNS is the contacts list.
DNS takes the website name you typed and looks up the number the internet actually needs to find it. That’s the whole job.
When you type netflix.com into your browser, your computer doesn’t actually go looking for a website called “netflix.com.” Computers don’t care about names. They only know how to find other computers by their IP address, a string of numbers like 192.0.2.10. That’s the “phone number” side of things.
Here’s where it gets even more like your phone. Your computer keeps its own little contacts list of websites you’ve visited recently. If netflix.com is already in there, it grabs the number instantly. If it isn’t, your computer asks a DNS server, which is like one giant shared contacts list for the whole internet: “Hey, what’s the number for netflix.com?” The server hands back the IP address, your computer saves it to its own contacts for next time, and only then does your browser connect to the website.
All of that happens in a fraction of a second, which is why it feels instant. But there’s a lookup happening behind the scenes every single time.
When you request netflix.com, your stub resolver first checks its local cache, then hands the query to a recursive resolver (usually your ISP’s, or something like 1.1.1.1 / 8.8.8.8). If the recursive resolver doesn’t have the answer cached, it walks the hierarchy: it asks a root server (“who handles .com?”), then the TLD nameserver (“who’s authoritative for netflix.com?”), then the authoritative nameserver, which finally returns the A record (or AAAA for IPv6).
Each answer carries a TTL, which is how long every resolver in the chain may cache it before asking again. Queries ride UDP port 53 by default (TCP for large responses and zone transfers), and increasingly DoH/DoT (DNS wrapped in HTTPS or TLS), so the names you look up aren’t readable in transit.
DNS is the internet’s contacts list: you pick a name, it finds the number.
Fun bit of trivia: that little contacts list your computer keeps is called a DNS cache. Sometimes a website moves to a new number and your computer keeps calling the old one, like a friend who changed numbers while your phone still has the old contact. That’s why “clear your DNS cache” is the tech-support equivalent of “have you tried turning it off and on again.” It makes your computer look the number up fresh.
You could! Try typing an IP address straight into your browser sometime. It usually works. But nobody wants to remember a string of digits for every site they visit, any more than you’d want to type in your dentist’s actual phone number instead of just tapping “Dentist.” Names are for humans. Numbers are for machines. DNS is the translator standing in between, doing the boring lookup work so you never have to.
A shocking number of “the internet is broken!” moments are actually just DNS having a bad day. If the lookup fails, your computer never gets the number, so it can’t connect to anything, even though the website itself is running just fine on the other end. That’s usually what’s behind the classic “This site can’t be reached” error. The house is home; you just couldn’t find its address.
Next time that happens, you can nod knowingly and say “must be a DNS thing.” You’ll be right more often than you’d expect.
The classic failure modes: your configured resolver is down or unreachable, a record’s TTL outlived a server move (stale cache), a domain’s NS delegation is broken, or DNSSEC validation fails and the resolver returns SERVFAIL. From a terminal, dig +short example.com (or nslookup on Windows) tells you in one line whether name resolution is the problem. If you get an IP back but the site still won’t load, your issue is not DNS.
And yes, the industry haiku is true often enough to be a meme: it’s not DNS / there’s no way it’s DNS / it was DNS.
One short email: the scam making the rounds, one tech word made simple, and one tip to keep you and your family safe. Free, no spam, unsubscribe anytime. Plus a free printable "How to Spot a Scam" sheet for your fridge.
We send one email to confirm it's really you. Your address stays with us and our email service, nobody else. Privacy
The cloud isn't in the sky. It's in giant, humming, refrigerated warehouses full of computers, and they're hungry for electricity and water. Here's what a data center is.
New phones are ditching the little SIM card tray. An eSIM is the same thing, built in and programmed over the air, like a hotel updating your key card without a trip to the front desk.
Click every traffic light. Now do it again. CAPTCHAs are bouncers that keep robots out, and if you keep failing them, the problem is probably your connection, not you.
