DNS.
The internet's phone book: it turns a name you can remember into the number a computer needs.
People remember names like example.com. Computers only know how to reach numeric addresses, like 93.184.216.34. DNS is the lookup that bridges the two, and it runs quietly every single time you open a site.
Think of it as asking directory assistance for a phone number before you can place the call. The call itself only happens once you have the number.
- Pizza. Now.1
You know the name — pizza.com — but computers only call numbers, never names.
- …what’s its number?!2
And a name is useless to a computer until it’s turned into an address.
- pizza.com — hurry!3
So your computer asks a resolver — the internet’s directory assistance.
- 4
The resolver races down a chain of address books until one of them knows the answer.
- Beautiful.5
Back comes the number — the address your computer needed all along.
- Next time: instant slice.6
It connects — and jots the number on a sticky note, so next time skips the whole hunt.
Why it is a chain, not one big book
No single computer could hold every name on the internet, so the phone book is split into levels. Root servers know who runs each ending (.com, .org). Those point to the servers for a specific domain. Those finally hold the actual addresses.
Your resolver walks down that chain once, then caches what it learned for a set time so it does not have to ask again for a while.
Why changes feel slow, and outages feel huge
Because answers are cached at many layers, when you change where a name points it can take hours for everyone to see the update — old answers linger until they expire.
And because DNS is the very first step of almost everything online, when it breaks the whole internet seems down even though the actual websites are running fine. A surprising number of big outages are really DNS problems.