What Is DNS? The Phonebook of the Internet Explained
Every time you type a web address into your browser, you're relying on the Domain Name System. DNS translates human-readable domain names like example.com into the IP addresses that computers use to find each other on the internet — the way a phonebook maps a person's name to their phone number. Without DNS, you'd have to memorize strings of numbers to visit any website.
How Resolution Actually Works
When you enter a URL, your device sends a query to a DNS resolver — typically run by your internet service provider or a third-party service. The resolver doesn't have every answer memorized. It begins a recursive lookup: first asking a root server where to find the .com zone, then querying the Top-Level Domain server for the specific domain, and finally reaching the authoritative nameserver that holds the actual IP address record. This entire chain completes in milliseconds or less under normal conditions.
Caching matters enormously. Resolvers store previous answers for a set time, called the Time to Live, so they don't have to repeat the full lookup for every request. That's why DNS changes — like switching web hosts — can take hours to propagate.
Recursive vs. Authoritative Servers
A recursive resolver does the legwork of chasing down answers on behalf of the client. An authoritative nameserver is the source of truth: it holds the actual DNS records for a domain and provides the definitive answer about where that domain points. In between sit the root and TLD nameservers, which don't hold domain records themselves but know exactly where to redirect queries for each zone. Together, this hierarchy is one of the internet's oldest and most resilient distributed systems.
DNS was designed in an era when trust was assumed, not earned. Modern threats like cache poisoning and DNS hijacking mean that technologies such as DNSSEC and DNS-over-HTTPS are increasingly important for verifying that the answer you get is genuine.