What is DNS? The internet's phonebook, explained properly

DNS — the Domain Name System — is the internet's phonebook. Computers find each other by numeric address; humans remember names. DNS is the service that translates one into the other, every single time you visit anything.

The lookup, step by step

Type a name and four quiet things happen. Your device asks a resolver (usually your ISP's, or a public one) to find the address. The resolver, if it does not already know, asks the root servers, which point it at the TLD servers for the ending (.com, .ng, .org), which point it at the domain's nameservers — the ones the domain's owner chose. The nameserver answers with the record: an A record holding the IPv4 address, AAAA for IPv6, CNAME for “same as that other name”, MX for where email goes, TXT for verification strings. The resolver caches the answer for as long as the record's TTL (time to live) allows, and hands it to your browser, which connects to the number.

Why this matters to you

Propagation is caching. When you change a DNS record, the change spreads as resolvers' caches expire — usually fast, occasionally hours, depending on the old TTL. “DNS propagation” is not a global switch flipping; it is cached answers politely dying at different times. We lived this exact sequence moving this very site: the DNS order that avoids downtime is our first-hand walkthrough. Email breaks by DNS — MX records are why mail stops when nameservers go wrong. And “site not found” errors are usually DNS, not the website being down.

The security angle, briefly

Because DNS is old and trusting, the industry has been adding verification: DNSSEC signs answers so they cannot be forged in transit, and browsers increasingly prefer encrypted DNS. You do not need to configure any of it to benefit — but knowing the phonebook can be tampered with explains a certain species of “why am I on the wrong site?” attack, the kind our link-reading guide teaches you to catch at the other end.

Sources

• Cloudflare Learning — What is DNS?