Networks route traffic using IP addresses — numbers. Humans remember names. You type rootandroute.online; the network needs something like 185.199.108.153. The Domain Name System (DNS) is the translation service between those two worlds, and it runs invisibly before nearly everything you do online.
The lookup, step by step
When you visit a site your device hasn't seen recently:
- Your device asks its configured DNS resolver (usually run by your router, ISP, or a public service): "what's the address for this name?"
- If the resolver doesn't know, it walks the name backwards — asking the internet's root servers who handles
.online, asking those who handlesrootandroute.online, and asking that server for the actual number. - The answer comes back and — crucially — gets cached (remembered) at every step, with an expiry time, so the next lookup is instant.
All of that typically takes a few dozen milliseconds, once, and then caching makes it free.
Why DNS failure looks like the end of the internet
Here's the diagnostic insight that earns this post its place on the trail: when DNS breaks, the network is usually fine — but nothing can find anything by name, so to the user, "the internet is down." The classic tell: websites fail by name, but a direct IP address still works. The phone book burned down; the phones are fine.
There's a running joke in operations: "It's always DNS." It's a joke because it's disproportionately true — DNS misconfiguration sits behind a remarkable share of major outages, partly because caching means mistakes propagate on a delay and fix on a delay too, which makes cause and effect maddeningly hard to line up.
Two more ideas you'll meet immediately
Records: DNS holds more than one kind of answer per name — an A record maps a name to an IPv4 address, CNAME aliases one name to another, MX says where email for the domain should go, TXT holds arbitrary text (used constantly for proving domain ownership). If you've ever set up a website or verified a domain with Google, you've edited these.
Propagation: because of caching, changing a DNS record doesn't update the world instantly — old answers live in caches until their expiry (TTL) runs out. That's why "DNS changes can take up to 48 hours" appears on every hosting guide ever written, and why patience is a legitimate troubleshooting step.