DNS Explained: The Internet's Phonebook
DNS turns names like example.com into the numbers computers need. Here's how DNS works, what happens when you change a record, and why it sometimes lags.
Every time you visit a site, something has to translate the human-friendly name into the numeric address computers actually use. That something is DNS — the Domain Name System — and it's so reliably invisible that most people never think about it until it breaks.
The phonebook analogy
You remember "Pizza Palace," not its phone number. A phonebook bridges the two. DNS does exactly this for the web: you type example.com; DNS finds the numeric IP address (like 93.184.216.34) so your browser knows which server to connect to.
How a lookup actually happens
When you request a name your computer doesn't already know, a resolver walks a short chain:
- Root servers point it toward the right top-level domain (".com", ".org"...).
- The TLD servers point it toward the domain's authoritative server.
- The authoritative server gives the final answer — the IP address.
It sounds slow, but it usually isn't, because of caching.
Caching: why it's fast (and why changes lag)
Once an answer is found, it's cached at many points — your device, your resolver, others — for a set time called the TTL (time to live). So the next lookup is instant. The flip side: when you change a DNS record (say, moving your site to a new server), the old answer lingers in caches until the TTL expires. That's why DNS changes "propagate" over minutes to hours rather than instantly.
DNS is fast because it caches everything, and frustrating to change for exactly the same reason.
Record types worth knowing
- A / AAAA — maps a name to an IPv4 / IPv6 address.
- CNAME — points one name at another name (an alias).
- MX — where to deliver email for the domain.
- TXT — free-form text, used for verification and email security (SPF, DKIM).
A practical tip
Planning to move a site or change servers? Lower the TTL a day in advance. Then when you flip the record, the change propagates quickly because caches were told to forget sooner. It's the single trick that makes DNS migrations painless — and it's the very first step in the journey of every web request.
Key takeaways
- DNS translates names into the IP addresses computers use.
- A lookup walks root → TLD → authoritative servers, then caches the result.
- Caching (TTL) makes lookups fast but delays record changes.
- Lower the TTL before a migration so changes propagate quickly.
Frequently asked questions
Why do DNS changes take time to update?
Because answers are cached all over the internet with a 'time to live' (TTL). Until that timer expires, some systems keep using the old answer. Lowering the TTL before a change makes updates propagate faster.
What is a DNS resolver?
It's the service (often run by your ISP or a public provider) that does the lookup work for you — asking the chain of DNS servers and caching the result so the next lookup is instant.