What is DNS? The Internet's Phone Book Explained Simply

What is DNS in Simple Terms?

Every time you type a website address into your browser — say google.com or youtube.com — something remarkable happens behind the scenes in a fraction of a second. Your computer does not actually know where "google.com" lives. It needs a number. Computers on the internet communicate using numerical addresses called IP addresses, which look something like 142.250.80.46. DNS is the system that translates the human-friendly name into that number.

DNS stands for Domain Name System. Think of it as the internet's phone book. Before mobile phones, if you wanted to call your friend Sarah, you did not dial a random number from memory — you looked up her name in the phone book and found her number. DNS does exactly the same thing, except it works for websites and it happens automatically, invisibly, in milliseconds.

Imagine the entire internet is a massive city. Every building (website) has a street address (IP address) like "142.250.80.46". DNS is the GPS that takes the name "Google HQ" and converts it to the address so your car (browser) can navigate there. Without DNS, you would need to memorize the street address of every website you visit.

Without DNS, the internet as we know it would not be usable. Nobody wants to memorize strings of numbers just to check their email. DNS solves that by letting humans use memorable names while computers use the numbers they need under the hood.

The Domain Name System was created in 1983 by Paul Mockapetris. Before that, every computer on the internet had to maintain a single text file called HOSTS.TXT that listed every known hostname and its IP address. As the internet grew, this approach became completely unmanageable. DNS replaced it with a distributed, hierarchical database that scales to handle billions of domains — and it still powers every website visit you make today.

How DNS Works Step by Step

The DNS lookup process involves several players working together almost instantaneously. Here is exactly what happens when you type itvedas.com into your browser and press Enter:

1. Your browser checks its own cache first. If you visited itvedas.com recently, your browser already remembers the IP address. It skips the lookup entirely and goes straight to the website. This is why pages you visit often seem to load faster.
2. Your operating system checks its local cache. If the browser does not have it, your computer's operating system checks its own DNS cache. Windows, macOS, and Linux all store recent lookups to speed things up.
3. Your device contacts the Recursive Resolver. If neither cache has the answer, your device sends a query to a DNS recursive resolver — usually a server operated by your internet service provider (ISP) or, if you have changed it, a public DNS like Google (8.8.8.8) or Cloudflare (1.1.1.1). This resolver does the heavy lifting on your behalf.
4. The resolver asks a Root Name Server. The root servers are like the top of the directory. There are 13 sets of root servers distributed around the world. They do not know where itvedas.com is, but they know who to ask next. They point the resolver to the right Top-Level Domain (TLD) server — in this case, the server responsible for all .com domains.
5. The resolver asks the TLD Name Server. The .com TLD server knows which specific name servers are authoritative for itvedas.com. It hands that information back to the resolver.
6. The resolver asks the Authoritative Name Server. This is the definitive source of truth for itvedas.com. It holds the actual DNS records and returns the IP address — for example, 76.76.21.21.
7. The resolver sends the IP address back to your device. It also caches the result so it does not have to look it up again for a while (the duration is set by a value called TTL — Time To Live).
8. Your browser connects to the website. Now that it has the IP address, your browser opens a connection to the web server at that address, and the page loads.

This entire sequence — from step 1 through step 8 — typically takes between 20 and 120 milliseconds. That is faster than the blink of an eye. You never see it happening, but it is running every single time you click a link or type a URL.

Think of the DNS lookup like calling directory assistance. You call and say "I need the number for Pizza Palace on Main Street." The operator checks their records and reads you the number. You write it down so you do not have to call again. The resolver is the operator, the root servers are the main switchboard, and the authoritative server is the specific local directory that has the exact listing.

What is DNS on WiFi — and Why Does It Matter?

When you connect your phone or laptop to a WiFi network — whether at home, in a coffee shop, or at the office — your device does not just get an IP address. It also receives the address of a DNS server to use. This happens automatically through a protocol called DHCP (Dynamic Host Configuration Protocol), which is the system your router uses to hand out network settings to every device that connects.

By default, your router assigns you the DNS server provided by your ISP (Internet Service Provider). This means every single website lookup you make — every domain name your apps and browsers need to resolve — flows through a DNS server that your internet company controls.

Why Does Your WiFi DNS Server Matter?

There are three main reasons the DNS server assigned by your WiFi network matters to you as an everyday user:

• Speed. Different DNS servers respond at different speeds. If your ISP's DNS server is slow or overloaded, every website you visit will feel slightly sluggish — not because the websites are slow, but because the address lookup takes longer. Switching to a faster DNS provider like Cloudflare's 1.1.1.1 or Google's 8.8.8.8 can noticeably improve browsing speed.
• Privacy. Your ISP's DNS server logs every domain you look up. This creates a detailed record of every website, app, and service you use. Some ISPs sell this data to advertisers. Using a privacy-focused DNS like 1.1.1.1 (Cloudflare) means your ISP no longer sees your lookups — Cloudflare does, and they have a strict no-logging policy.
• Security. Some DNS providers offer built-in protection against malicious websites. For example, Cloudflare's 1.1.1.1 for Families or OpenDNS can block known malware and phishing domains before your browser even connects to them.

On a home network, you can change your DNS settings either on your router (which applies the change to every device automatically) or on individual devices. On public WiFi — like at a hotel or airport — you generally cannot change the router settings, but you can still change the DNS on your own device.

Types of DNS Servers Explained

Not all DNS servers do the same job. The DNS system is built around specialization — different types of servers handle different parts of the lookup process. Understanding the four main types will help you make sense of how the whole system fits together.

1. Recursive Resolver (Recursive DNS Server)

This is the server your device talks to first. It is sometimes called a "DNS recursor" or "recursive nameserver." Think of it as your personal research assistant. When you ask it for the IP address of a domain, it does not just say "I don't know." Instead, it goes and finds the answer by querying other servers on your behalf. Most people's recursive resolver is operated by their ISP, but you can change it to a public option like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).

2. Root Name Servers

These are the top of the DNS hierarchy. There are 13 logical root server addresses (operated by various organizations worldwide, with hundreds of physical machines behind them using a technique called Anycast routing). Root servers do not know where your specific website is — they know which servers are responsible for each top-level domain like .com, .org, or .uk. They point the resolver in the right direction.

3. TLD Name Servers (Top-Level Domain)

Each top-level domain — .com, .net, .org, country codes like .uk or .in — has its own set of name servers. When the recursive resolver is looking for itvedas.com, the root server sends it to the .com TLD server. That server knows which authoritative name servers hold the records for itvedas.com.

4. Authoritative Name Servers

This is the final stop. The authoritative name server holds the actual DNS records for a specific domain. When you register a domain and set up hosting, you configure authoritative name servers that store your DNS records — including the A record (which maps your domain to an IP address), MX records (for email), CNAME records (aliases), and more. This server gives the definitive, authoritative answer: "itvedas.com is at this IP address."

How to Check and Change Your DNS

Checking and changing your DNS server is easier than most people think. Here is how to do it on the most common platforms.

How to Find Your DNS Server on Windows

1. Press Windows + R, type cmd, and press Enter to open Command Prompt.
2. Type ipconfig /all and press Enter.
3. Look for the section for your active network adapter (Wi-Fi or Ethernet).
4. Find the line that says "DNS Servers" — the addresses listed there are your current DNS servers.

To change your DNS on Windows: go to Settings → Network & Internet → your connection → DNS server assignment → Edit → Manual, then enter your preferred DNS addresses.

How to Find Your DNS Server on Mac

1. Open System Settings (or System Preferences on older macOS).
2. Click Network.
3. Select your active connection (Wi-Fi or Ethernet).
4. Click Details (or Advanced on older macOS), then click the DNS tab.
5. The servers listed are your current DNS servers.

How to Change DNS on Android

On Android, you can use the Private DNS feature to set a DNS-over-HTTPS or DNS-over-TLS provider system-wide. Go to Settings → Network & Internet → Private DNS and enter a hostname like one.one.one.one for Cloudflare.

Recommended Public DNS Servers

• Cloudflare: Primary 1.1.1.1 / Secondary 1.0.0.1 — fastest public DNS, strong privacy policy
• Google: Primary 8.8.8.8 / Secondary 8.8.4.4 — reliable, well-known
• OpenDNS: Primary 208.67.222.222 / Secondary 208.67.220.220 — optional filtering features
• Quad9: Primary 9.9.9.9 / Secondary 149.112.112.112 — security-focused, blocks malware domains

Common DNS Problems and How to Fix Them

DNS errors are among the most common internet problems people encounter, but they are usually straightforward to diagnose and fix. Here are the most frequent DNS issues and what to do about them.

DNS_PROBE_FINISHED_NXDOMAIN

This Chrome error means the DNS lookup for a domain returned "non-existent domain" (NXDOMAIN). The domain name could not be resolved to an IP address. This can happen because: the domain genuinely does not exist or was typed incorrectly; your DNS server is having trouble; or the domain's DNS records have a problem.

Fix: Double-check the URL spelling. Try flushing your DNS cache: on Windows run ipconfig /flushdns in Command Prompt; on Mac run sudo dscacheutil -flushcache in Terminal. Try switching to a different DNS server like 8.8.8.8.

Websites Load on Mobile Data but Not WiFi

This classic symptom almost always points to a DNS problem on the WiFi network. Your mobile connection uses a different DNS server (your cellular carrier's), so it works fine. Your WiFi network's DNS server is broken, blocked, or misconfigured.

Fix: On your device, manually set a public DNS like 1.1.1.1 instead of using the one assigned by the router. Alternatively, restart your router — sometimes the DNS server assignment gets corrupted and a reboot clears it.

Intermittent DNS Failures

Sometimes DNS works, sometimes it does not. Pages time out randomly. This usually indicates your ISP's DNS server is overloaded or experiencing issues.

Fix: Switch to a faster, more reliable public DNS provider. Cloudflare's 1.1.1.1 is widely considered the fastest and most reliable public DNS resolver available.

Slow Website Loading Despite Fast Internet

If you have a fast internet connection but websites feel slow to start loading (there is a delay before anything happens), DNS resolution time could be the bottleneck. Each new domain your browser encounters needs a DNS lookup before the connection can start.

Fix: Switch to a geographically nearby, high-performance DNS resolver. Run a DNS benchmark tool to compare response times from your location and pick the fastest option.

Frequently Asked Questions

What is DNS?

DNS (Domain Name System) is the internet's phone book. It translates human-readable domain names like google.com into IP addresses like 142.250.80.46 that computers use to find and connect to websites. Without DNS, you would need to memorize numerical addresses for every website you visit.

What is DNS on WiFi?

When you connect to WiFi, your router automatically assigns your device a DNS server to use — usually one operated by your ISP. Every domain name your device looks up (for websites, apps, email, etc.) goes through this DNS server. You can change it to a faster or more private option like Cloudflare's 1.1.1.1, either on your router (for all devices) or on individual devices.

What is a DNS server?

A DNS server is a computer that maintains a directory of domain names and their corresponding IP addresses. When you type a URL in your browser, your device contacts a DNS server to ask "what is the IP address for this domain?" The server either answers from its own records or looks up the answer from other DNS servers and relays it back to you.

What happens if DNS fails?

If your DNS server fails or becomes unreachable, you cannot reach websites by name. Your browser will display errors like DNS_PROBE_FINISHED_NXDOMAIN, "This site can't be reached," or "Server not found." The underlying internet connection is still working — packets can still travel — but your device cannot translate domain names into IP addresses, so no websites load.

How do I find my DNS server?

On Windows: open Command Prompt and run ipconfig /all, then look for the "DNS Servers" line under your active network adapter. On Mac: go to System Settings → Network → your connection → Details → DNS tab. On Android/iOS: check your WiFi connection settings — some versions show DNS directly; otherwise use a DNS lookup app or check your router's admin page.