How DNS Works: A Complete Guide for Developers
📖 8 min read · Network Tools · Try DNS Lookup Tool →
What is DNS?
DNS stands for Domain Name System. It is the internet's phonebook — a distributed database that translates human-readable domain names like devbench.site into machine-readable IP addresses like 76.76.21.21. Without DNS, you would need to memorize the IP address of every website you visit.
DNS was created in 1983 by Paul Mockapetris to replace a single HOSTS.TXT file that mapped hostnames to IP addresses. As the internet grew, a centralized file became unmanageable. DNS solved this with a hierarchical, distributed system that scales to billions of domains.
How DNS Resolution Works Step by Step
When you type a URL into your browser, a DNS resolution process happens in milliseconds. Here is exactly what occurs:
- Browser cache check — Your browser first checks its own DNS cache. If you visited the site recently, the IP address is stored locally and the lookup is instant.
- Operating system cache — If not in the browser cache, the OS checks its own DNS cache and the local hosts file (/etc/hosts on Linux/Mac, C:\Windows\System32\drivers\etc\hosts on Windows).
- Recursive resolver — If still not found, the query goes to your ISP's recursive DNS resolver (or a public resolver like 8.8.8.8 or 1.1.1.1). This resolver does the heavy lifting on your behalf.
- Root nameservers — The resolver queries one of 13 root nameserver clusters. These don't know the IP address but know which nameservers handle each top-level domain (.com, .org, .site, etc.).
- TLD nameservers — The root server directs the resolver to the TLD nameserver (e.g., Verisign for .com). The TLD server knows which nameservers are authoritative for the specific domain.
- Authoritative nameserver — The resolver queries the domain's authoritative nameserver (usually your hosting provider or Cloudflare). This server has the actual DNS records and returns the IP address.
- Response cached and returned — The resolver caches the result for the duration of the TTL (Time to Live) and returns the IP to your browser. Your browser connects to the server at that IP.
This entire process typically takes 20–120 milliseconds on the first visit. Subsequent visits are much faster due to caching.
What is an IP Address?
An IP (Internet Protocol) address is a unique numerical label assigned to every device connected to a network. It serves two purposes: identifying the host and providing the location for routing data packets.
There are two versions of IP addresses in use today:
- IPv4 — 32-bit addresses written as four numbers separated by dots, e.g.,
192.168.1.1. Supports ~4.3 billion unique addresses. Nearly exhausted. - IPv6 — 128-bit addresses written as eight groups of hexadecimal digits, e.g.,
2001:0db8:85a3:0000:0000:8a2e:0370:7334. Supports 340 undecillion addresses — effectively unlimited.
IPv4 vs IPv6: Key Differences
| Feature | IPv4 | IPv6 |
|---|---|---|
| Address length | 32 bits | 128 bits |
| Format | Decimal (192.168.1.1) | Hexadecimal (2001:db8::1) |
| Total addresses | ~4.3 billion | 340 undecillion |
| NAT required | Yes (address shortage) | No |
| Security | Optional (IPSec) | Built-in (IPSec mandatory) |
| Header size | 20 bytes | 40 bytes (simpler structure) |
| Adoption | ~70% of traffic | ~30% and growing |
DNS Record Types Explained
DNS records are instructions stored in authoritative nameservers that tell the DNS system what to do with queries for a domain. Here are the most important record types:
Maps a domain to an IPv4 address. The most fundamental DNS record. Example: devbench.site → 76.76.21.21
Maps a domain to an IPv6 address. Same as A record but for IPv6. Example: devbench.site → 2606:4700::6810:1523
Canonical Name — creates an alias from one domain to another. Example: www.devbench.site → devbench.site. Cannot be used on the root domain.
Mail Exchange — specifies the mail servers responsible for receiving email for the domain. Has a priority value; lower number = higher priority.
Text records store arbitrary text data. Used for domain verification (Google, GitHub), SPF records (email authentication), DKIM keys, and DMARC policies.
Nameserver records specify which DNS servers are authoritative for the domain. These point to your hosting provider's nameservers.
Start of Authority — contains administrative information about the zone including the primary nameserver, admin email, and serial number.
Pointer record — the reverse of an A record. Maps an IP address back to a domain name. Used for reverse DNS lookups and email server verification.
Service record — specifies the location of servers for specific services. Used by protocols like SIP, XMPP, and Microsoft services.
Certification Authority Authorization — specifies which certificate authorities are allowed to issue SSL certificates for the domain.
What is TTL (Time to Live)?
TTL is a value in DNS records that tells resolvers how long to cache the record before querying the authoritative nameserver again. It is measured in seconds.
- Low TTL (300–600 seconds) — Changes propagate quickly (5–10 minutes). Use when you plan to change DNS records soon. Higher load on nameservers.
- Medium TTL (3600 seconds / 1 hour) — Good balance for most sites. Changes take up to 1 hour to propagate globally.
- High TTL (86400 seconds / 24 hours) — Fastest resolution for visitors (heavily cached). Changes take up to 24 hours to propagate. Use for stable records.
Pro tip: Before migrating a website, lower your TTL to 300 seconds 24–48 hours in advance. This ensures DNS changes propagate quickly during the migration window.
DNS Troubleshooting Guide
When DNS isn't working correctly, here are the most common issues and how to diagnose them:
Site not loading after DNS change
DNS propagation takes time. Old records are cached by resolvers worldwide. Use our DNS Lookup tool to check what records different nameservers are returning. If the authoritative nameserver shows the new record but your browser doesn't, clear your browser DNS cache (chrome://net-internals/#dns in Chrome) or flush your OS DNS cache.
Email not being received
Check your MX records using the DNS Lookup tool. Verify SPF records (TXT record starting with "v=spf1") are correctly configured. Missing or incorrect MX records are the most common cause of email delivery failures.
SSL certificate errors after DNS change
If you moved to a new host and SSL isn't working, check that your A record points to the new server IP and that the SSL certificate has been issued for the new server. Check CAA records to ensure your certificate authority is allowed.
Slow DNS resolution
Use our Network Speed Test and IP Lookup to check your connection. Consider switching to a faster public DNS resolver: Cloudflare (1.1.1.1), Google (8.8.8.8), or Quad9 (9.9.9.9).
Network Debugging Tools
As a developer, these tools are essential for diagnosing network and DNS issues:
- nslookup / dig — Command-line tools for querying DNS records.
dig devbench.site Areturns the A record. - ping — Tests connectivity to a host and measures round-trip time.
ping devbench.site - traceroute / tracert — Shows the path packets take to reach a destination, identifying where delays or failures occur.
- curl — Tests HTTP responses from the command line.
curl -I https://devbench.siteshows response headers. - whois — Looks up domain registration information including registrar, owner, and expiration date.
Use our free online tools for quick lookups without leaving your browser: