What Is DNS?

Acutis · plain-English network help · updated June 2026

What is DNS, in plain English?

DNS stands for the Domain Name System. The simplest way to think about it: DNS is the internet's phone book. People remember names like wikipedia.org, but computers and routers find each other using numbers called IP addresses, such as 198.35.26.96. DNS is the system that translates the human-friendly name you type into the numeric address your device actually needs to make a connection.

Every time you open a website, send an email, or load an app, a DNS lookup happens quietly in the background. You almost never notice it — until it stops working. When DNS fails, you can be fully connected to your network and still get errors like "server not found," even though the rest of the internet is fine.

How a DNS lookup actually works

When you type a web address, your computer doesn't already know the number behind it. It asks a chain of servers, each one pointing it closer to the answer. Here is the journey, step by step:

1. Your browser checks its memory first. Browsers and your operating system keep a short-term cache of recent lookups. If the name was looked up recently, the answer is reused instantly and the rest of these steps are skipped.
2. The request goes to a resolver. This is usually a DNS server run by your internet provider, or a public one like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare). The resolver does the legwork on your behalf.
3. The resolver asks a root server. Root servers don't know the final answer, but they know who handles each top-level ending, such as .com, .org, or .net. They reply, "ask the .com servers."
4. Then a TLD server. The "top-level domain" (TLD) server for .com knows which name servers are responsible for a specific domain. It replies, "ask the servers that handle example.com."
5. Finally, the authoritative server. This is the server that actually holds the real record for the domain. It returns the IP address — the final number your computer needs.

Your resolver hands that address back to your browser, which then connects to the website. The whole round trip usually takes a few thousandths of a second, and the answer is cached so the next visit is even faster.

Why DNS matters to you

DNS sits in front of nearly everything you do online, so when it is slow or broken, the whole internet feels slow or broken — even when your connection is perfectly healthy. A few reasons it matters:

• Speed. A slow or distant DNS resolver adds a small delay to the first connection of every new site you visit. A fast resolver can make general browsing feel snappier.
• Reliability. If your provider's DNS server has an outage, you may be unable to reach websites by name even though your link to the internet is fully up.
• Privacy and safety. Some DNS providers filter out known malicious or scam domains before you ever connect, adding a layer of protection.

Common DNS problems and confusions

A few patterns come up again and again. Recognizing them saves a lot of guesswork:

• "Connected, but no websites load." This is the classic DNS symptom. Your Wi-Fi shows connected, but names won't resolve. A quick test: if a numeric address works but names don't, DNS is the likely culprit.
• Stale cache. If a website recently moved to a new server, your computer may keep using the old cached address for a while. Clearing the DNS cache (sometimes called "flushing") forces a fresh lookup.
• The wrong resolver. An overloaded or far-away DNS server can make every site feel sluggish to start. Switching to a fast public resolver often helps.
• Confusing DNS with your connection. DNS failing does not mean your internet is down. The cable, router, and signal can all be perfect while DNS alone is the broken link.

A quick way to test DNS yourself

If pages won't load, try opening a site you know by a numeric address you trust, or run a name lookup from a command line. If the number connects but the name fails, you've isolated the problem to DNS rather than your physical connection. From there, switching DNS servers or flushing the cache usually clears it. The key takeaway is that DNS is a separate layer — it can break on its own, and it can be fixed on its own.