How Does DNS Work? A Simple Guide to the Internet's Phone Book
✦ Key takeaways
- DNS translates human-friendly names like marifa.net into the numeric IP addresses machines actually use.
- A lookup passes through four stops: the resolver, a root server, a top-level domain (TLD) server, and the authoritative name server.
- Caching and the TTL value make repeat visits almost instant without repeating the full journey.
- Each domain has different records: A and AAAA for addresses, MX for mail, CNAME for aliases, and TXT for verification.
- Changing DNS records can take time to propagate worldwide, depending on the TTL that was set.
Every time you type a website name into your browser, a hidden journey begins that usually finishes in under a tenth of a second. You type an easy-to-remember name like marifa.net, but network devices don't know names; they speak in numeric addresses called IP addresses. The system that turns the name into a number is the Domain Name System, or DNS for short.
Why do we need DNS at all?
Imagine having to memorize a number like 172.67.183.24 for every site you visit instead of its name. The internet would be almost unusable. DNS works like a giant, distributed phone book: you know the person's name, and the book gives you their number. The difference is that this book is spread across millions of servers worldwide, is constantly updated, and has no single central copy.
Invoice & Quotation Maker
Professional invoices that auto-calc & print/PDF in a minute.
The four stops of any lookup
When the address isn't already cached on your device, the request passes through four ordered stops. First is the Resolver, usually a server run by your internet provider or a public service such as 1.1.1.1, whose job is to manage the search on your behalf. The resolver then asks a Root server, which doesn't know the address but points it in the right direction.
Next the question moves to the Top-Level Domain (TLD) server responsible for the extension, such as .net or .com, which in turn points to the Authoritative name server for that specific domain. This last server is the only one holding the final answer: the site's real IP address. The resolver returns the address to your device, and the browser connects to the server to fetch the page.
The lookup journey at a glance
| Stop | Who asks | What it returns |
|---|---|---|
| Resolver | Your device | Manages the whole search for you |
| Root server | Resolver | Points to the right extension server |
| TLD server | Resolver | Points to the domain's authoritative server |
| Authoritative | Resolver | Returns the final IP address |
Caching: why the journey isn't repeated every time
If those four stops repeated on every click, the internet would feel slow. So each level stores the answer temporarily for a set period called the TTL (time to live, in seconds). If you revisit the same site minutes later, the answer comes straight from the cache on your device or the resolver, with no new journey. This caching is why a second visit is always faster than the first.
The most common record types
A single domain doesn't hold just one address but a set of records, each with a function. An A record links the name to an IPv4 address, while an AAAA record links it to the newer IPv6 address. An MX record defines the mail server that receives your messages, a CNAME creates an alias pointing to another name, and a TXT record is used for ownership verification and email protection.
| Record | Function | Example use |
|---|---|---|
| A | Links name to an IPv4 address | Point marifa.net to the site server |
| AAAA | Links name to an IPv6 address | Same purpose, newer generation |
| CNAME | Alias pointing to another name | Map www to the root domain |
| MX | Defines the mail-receiving server | Route the domain's email |
| TXT | Text for verification and settings | Prove ownership, protect email |
Propagation: why a change isn't instant
When you change your domain settings — such as moving your site to new hosting — not everyone sees the change at the same moment. The reason is that servers around the world still hold the old answer in their cache until the TTL expires. That's why it's wise to lower the TTL ahead of any planned move so the change spreads faster once you make it.
DNS, privacy and security
Because DNS queries were traditionally sent in plain text, parties on the network could see which sites you visit even if their content was encrypted. That's why modern techniques like DNS over HTTPS emerged, encrypting these queries and protecting your privacy. Choosing a trusted resolver that supports encryption is a simple step that improves your security with no complexity.
The bottom line
The Domain Name System is the silent infrastructure that makes the internet usable with names instead of numbers. From resolver to authoritative server, a complex journey completes in a fraction of a second, and caching makes it nearly instant next time. Understanding this mechanism helps you diagnose connection problems and manage your domain with confidence.