What Is DNS? How Domain Name Resolution Works

DNS: The Internet's Phonebook

The Domain Name System (DNS) is one of the most fundamental technologies underpinning the modern internet. Every time you type a URL into your browser — say, example.com — your computer needs to find the numerical IP address that actually hosts that website. DNS is the system that makes this translation possible.

Without DNS, you would have to memorize IP addresses like 93.184.216.34 instead of simply typing example.com. DNS acts like a massive, distributed phonebook that maps easy-to-remember domain names to the IP addresses computers actually use to communicate.

The system is hierarchical and distributed across thousands of servers worldwide, making it both resilient and fast. Understanding how DNS works helps you diagnose connectivity problems, improve privacy, and understand why security issues like DNS cache poisoning are so dangerous.

• DNS stands for Domain Name System
• It translates domain names (like google.com) into IP addresses
• It is hierarchical: root servers → TLD servers → authoritative servers
• Without DNS, the web as we know it would not exist

How DNS Resolution Works Step by Step

When you enter a domain name in your browser, a multi-step lookup process called DNS resolution begins. Here is exactly what happens:

1. Browser cache check: Your browser first checks its own cache to see if it already knows the IP for this domain.
2. OS cache check: If not found, your operating system checks its own DNS cache and the local hosts file.
3. Recursive resolver query: Your OS asks a recursive DNS resolver — usually provided by your ISP or a public DNS like 8.8.8.8.
4. Root server query: If the resolver doesn't have the answer cached, it queries one of 13 sets of root name servers to find out which server handles the TLD (like .com).
5. TLD server query: The root server directs the resolver to the appropriate Top-Level Domain (TLD) server.
6. Authoritative name server query: The TLD server points to the authoritative name server for the specific domain, which holds the actual DNS records.
7. Record returned: The authoritative server returns the IP address, which is cached and delivered to your browser.

This entire process typically takes under 50 milliseconds, yet it's invisible to the end user. You can look up IP address information to see the resolved address for any domain.

DNS Servers: Resolvers, Root, TLD, and Authoritative

The DNS hierarchy involves four distinct types of servers, each playing a specific role:

Recursive Resolver: This is the first stop after your device. Operated by your ISP or a public DNS provider (like Google's 8.8.8.8 or Cloudflare's 1.1.1.1), it does the heavy lifting of querying other servers on your behalf. It also caches results to speed up future lookups.

Root Name Servers: There are 13 sets of root servers (labeled A through M) distributed globally. They don't know where every domain is, but they know which servers handle each TLD extension like .com, .org, or .net.

TLD Name Servers: These servers are responsible for top-level domains. Verisign, for example, operates the TLD servers for .com and .net.

Authoritative Name Servers: These hold the actual DNS records for a domain. When you register a domain and set up hosting, you configure these servers to point to the right IP addresses. The records here are the ultimate source of truth.

If you suspect DNS issues are affecting your browsing, run a DNS leak test to see which servers your system is actually using.

DNS Caching and TTL

DNS caching is a performance optimization that stores the results of DNS lookups for a period of time, preventing the need to repeat the full resolution process on every request. Both your browser and your operating system maintain DNS caches.

Every DNS record has a Time To Live (TTL) value, measured in seconds. This tells resolvers how long to cache the record before checking for an updated value. Common TTL values range from 300 seconds (5 minutes) to 86400 seconds (24 hours).

TTL has real-world implications. When you change your domain's DNS settings — for example, pointing it at a new server after migrating hosting — the change won't be visible to all users instantly. Old records will persist in caches until their TTL expires. This is known as DNS propagation.

If you're experiencing stale DNS issues after making changes, you can flush your local DNS cache to force a fresh lookup. This is one of the most common troubleshooting steps for web developers and sysadmins.

• TTL controls how long records are cached
• Lower TTL = faster propagation, more queries
• Higher TTL = slower propagation, fewer queries
• Browsers, OS, and resolvers all maintain separate caches

DNS Privacy and Security Concerns

Standard DNS queries are sent in plain text, meaning your ISP, network administrator, or anyone monitoring your traffic can see every domain you look up. This creates significant privacy concerns — even if the websites you visit use HTTPS, your DNS queries reveal your browsing habits.

Several technologies have been developed to address this:

• DNS over HTTPS (DoH): Encrypts DNS queries inside HTTPS traffic, preventing interception. Learn more about DoH.
• DNS over TLS (DoT): Similar to DoH but uses a dedicated port (853) instead of HTTPS.
• DNSSEC: Adds cryptographic signatures to DNS records to prevent tampering, protecting against DNS cache poisoning attacks.

If privacy matters to you, consider switching to a privacy-respecting public DNS provider like Cloudflare (1.1.1.1) or NextDNS, and enable DoH in your browser settings. Always run a DNS leak test after changing your DNS configuration to verify the change took effect.

Common DNS Problems and How to Fix Them

DNS issues are among the most common causes of website connectivity problems. Here are the most frequent issues and their fixes:

"DNS_PROBE_FINISHED_NXDOMAIN": This error means the domain was not found. The domain may not exist, be mistyped, or your DNS server may be unable to resolve it. Try flushing your DNS cache or switching to a different DNS server.

Slow page loads: If DNS resolution is taking too long, it adds latency to every web request. Switching to a faster public DNS server like 1.1.1.1 can dramatically improve browsing speed. See our guide on the best public DNS servers.

Website works on some devices but not others: This is usually a caching issue. Different devices cache DNS records independently. Clear the cache on the affected device or wait for the TTL to expire.

Changes not taking effect: After updating DNS records, propagation can take up to 48 hours due to caching. Learn more about DNS propagation and how to check its status.

Frequently Asked Questions