Explainers · Explainer
What Is DNS? A Plain Explanation

Short answer
DNS is the system that turns a domain name such as example.com into the IP address of the server that hosts the site. When you type a name, your device asks a resolver, which asks a chain of nameservers until one returns the address. The whole lookup runs in a fraction of a second, before the page starts to load.
Key takeaways
- DNS turns a domain name into the IP address of the server that hosts the site.
- A lookup passes through four servers: the recursor, the root nameserver, the TLD nameserver, and the authoritative nameserver.
- An uncached lookup has 8 steps, and caching skips most of them on repeat visits.
- Each DNS record carries a TTL in seconds, which sets how long other servers may cache the answer.
- Cloudflare 1.1.1.1 is free, keeps logs for 24 hours, and does not sell user data.
- Google Public DNS runs at 8.8.8.8 and 8.8.4.4, with no service level agreement on the free service.
What is DNS?
DNS is the system that turns a domain name such as example.com into the IP address of the server that hosts the site.
DNS stands for Domain Name System. Cloudflare's learning page calls it the phonebook of the Internet: humans use domain names, browsers use IP addresses, and DNS translates one into the other so pages can load.
Every device on the internet has its own IP address. Cloudflare notes that DNS removes the need to memorize addresses such as 192.168.1.1, the IPv4 form, or 2400:cb00:2048:1::c629:d7a2, the longer IPv6 form.
Without DNS, you would need to know the number of every site you visit. With it, you type a name and the system finds the number for you, in a fraction of a second, before the page even starts to load.
How does DNS work?
When you type a domain name, your device asks a resolver, which then asks a chain of nameservers until one returns the IP address.
The lookup runs behind the scenes and needs no action from you apart from the first request. Cloudflare explains that the process turns what you typed into the machine-friendly address needed to find the page.
When nothing is cached, the lookup has 8 steps. First you type the name and the query reaches a recursive resolver. The resolver asks a root nameserver, which points to the server for the top-level domain, such as .com.
The resolver then asks that TLD server, which points to the domain's own nameserver. The resolver asks that last server, and the IP address comes back to your browser.
The browser then makes its HTTP request to that IP address, and the server at that address returns the page. Cloudflare notes that the lookup itself is only the first half of the trip; the page fetch starts once the address is known.
Caching skips most of those steps on repeat visits. Cloudflare explains that DNS answers can be stored in the browser, in the operating system, and in the resolver, so the next lookup for the same name is almost instant.
What are the 4 servers in a DNS lookup?
Four servers handle a lookup: the recursor, the root nameserver, the TLD nameserver, and the authoritative nameserver.
The DNS recursor is the first stop. Cloudflare compares it to a librarian who is asked to find a book: it takes the query from your browser and makes the further requests needed to answer it.
The root nameserver is the first step in the chain. It works like an index in a library, pointing to more specific locations, and it answers with the address of the TLD server for endings such as .com or .org.
The root system is bigger than it sounds. The Root Server Technical Operations Association lists 389 root server sites, all operational, as read in November 2026.
The TLD nameserver hosts the last part of the hostname. For example.com, the .com server holds the pointer to the nameserver that handles example.com itself.
The authoritative nameserver is the last stop. Cloudflare describes it as the dictionary on the shelf: it actually holds the domain's records and returns the IP address for the name you asked about. It is the final source of truth for that domain.
| Server | Job in the lookup |
|---|---|
| DNS recursor | Takes your query and chases the answer for you |
| Root nameserver | Points to the right top-level domain server |
| TLD nameserver | Points to the domain's own nameserver |
| Authoritative nameserver | Holds the domain's records and returns the IP address |
What are DNS records?
DNS records are the entries that tell the internet where your domain's website, email, and other services live.
Each record has a type, a name, and a value. The type says what kind of answer it holds. Cloudflare's API docs list the standard types, including A, AAAA, CNAME, MX, NS, and TXT, and state that each record carries a TTL in seconds.
An A record points a name at an IPv4 address, and an AAAA record does the same job for an IPv6 address. A CNAME record makes one name an alias of another, so www.example.com can point at example.com instead of holding its own address.
An MX record names the mail servers for a domain, so email knows where to go. A TXT record holds plain text, which services use for checks such as proving you own the domain or setting mail rules.
An NS record lists the nameservers that hold the zone. Cloudflare's learning page notes that the resolver can cache NS records, which lets it skip the root and TLD steps and ask the domain's nameservers directly.
What is a DNS resolver, and which one should you use?
A DNS resolver is the server that looks up the IP address for you, and most people use the one their internet provider assigns.
Your router usually hands you your provider's resolver without asking. That works, but it is not your only option. Cloudflare's learning path names three free public resolvers: Cloudflare 1.1.1.1, Google 8.8.8.8, and OpenDNS.
Cloudflare's 1.1.1.1 is a free public resolver that does not sell user data to advertisers. Cloudflare states that it has been measured as the fastest DNS resolver available, and that its logs are kept for 24 hours for debugging, then purged.
Google Public DNS is the other well-known choice. Google's docs list its IPv4 addresses as 8.8.8.8 and 8.8.4.4, and its IPv6 addresses as 2001:4860:4860::8888 and 2001:4860:4860::8844. Google notes that there is no service level agreement for the free service.
Both support encrypted lookups. Cloudflare notes that 1.1.1.1 supports DNS over HTTPS and DNS over TLS, which wrap your query so it cannot be read on the way. Note that 1.1.1.1 only secures DNS queries; the WARP app is what secures all of your traffic.
How long does a DNS change take?
A DNS change can take minutes to reach some devices and much longer to reach others, because old answers stay cached until their TTL runs out.
Every DNS record carries a time-to-live, or TTL, which is the number of seconds other servers may keep the answer before checking again. Cloudflare explains that caching stores data closer to the person asking, so the query can be answered earlier and the rest of the chain can be skipped.
That cache is why a change does not show everywhere at once. Your browser may hold the old address, your operating system may hold it too, and your provider's resolver may hold it longer still, each for its own TTL.
Lower the TTL before you make a big change, such as moving hosts. A short TTL means caches expire fast, so the new address spreads quickly. Raise it again after the move, so lookups stay fast.
Our guide on how long DNS propagation takes explains the timing in detail, including which caches matter most when you move a WordPress site.
What goes wrong with DNS?
Most DNS problems come from wrong records, stale cache, or a domain that points at the wrong server.
The most common error is a wrong A record. If the record points at an old server, visitors reach the old site or nothing at all, even though the domain itself is fine.
Check the record value first, then check that the domain's nameservers are the ones your host or Cloudflare gave you.
The second cause is cache. If you fixed the record but your browser still shows the old site, the old answer is still cached somewhere. Cloudflare notes that in Chrome you can view the browser's DNS cache at chrome://net-internals/#dns, and clearing it is the quickest check.
The third cause is a missing record. If a subdomain such as shop.example.com has no A or CNAME record, the lookup fails and the browser shows a DNS error. Our guide on fixing DNS probe finished NXDOMAIN walks through that error step by step.
The fourth cause is a domain that expired or was never pointed at your host. Our guide on how to point a domain to WordPress hosting shows how to set the nameservers and the A record correctly.
How do you check your DNS settings?
You check DNS with a lookup tool, your domain registrar's DNS panel, or a command such as nslookup on your own computer.
Start with a public lookup tool and ask for the A record of your domain. The answer should be your host's IP address, not an old one. Then ask for the NS records: they should list the nameservers your host or Cloudflare gave you.
Next, open your registrar's DNS panel and compare the records there with what the lookup tool returns. If the panel is right but the lookup is wrong, the old answer is still cached somewhere, and waiting for the TTL to run out is the fix.
You can also switch your own resolver to test faster. Cloudflare states that 1.1.1.1 is completely free and takes minutes to set up.
Open your computer's internet preferences and replace the existing DNS address with 1.1.1.1. Our guide on how to set up Cloudflare for WordPress covers the full setup, including the DNS step.
Frequently asked questions
Is DNS the same thing as web hosting?
No. DNS only turns the domain name into an IP address so your browser can reach the server. Your host stores the site's files, and the domain registrar holds the domain itself. DNS is the lookup step that connects the two.
Should I change my DNS resolver from my internet provider's?
Your internet provider assigns a resolver by default, but you can switch to a free public one. Cloudflare 1.1.1.1 and Google 8.8.8.8 are the best known. Both are free, and both support encrypted lookups that hide your queries from snooping networks.
I changed a DNS record but my site still shows the old version. Why?
Wait for the TTL to run out, or clear the cache that holds the old answer. Check the browser cache first, then the operating system cache. Public lookup tools show what the rest of the internet sees, which tells you whether the problem is only on your device.
Will changing a DNS record break my email?
No. A DNS change only affects the name you changed, and only after caches expire. Other records for the same domain keep working as before, and nothing about the site's files changes unless you also move the hosting.
Do I need DNS records for email as well as for my website?
Yes, if your mail uses the same domain. MX records tell the world which servers accept mail for your domain, and they sit next to the A records in the same DNS zone. If you move the zone to a new provider, copy the MX records across first.
Sources
- What is DNS? How DNS Works Cloudflare
- What is 1.1.1.1? Cloudflare
- Get Started with Google Public DNS Google for Developers
- Root Server Sites Root Server Technical Operations Association
- Create DNS Record, Cloudflare API Cloudflare Developers
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


