To your browser, droidcrunch.com is two numbers: 104.21.22.36 and 172.67.202.60. Nobody types those, so something has to translate.
That something is DNS. It answered most of our test lookups in 3 to 15 milliseconds.
One wrong letter was the slow exception. Ending the name in “.con” took 407 milliseconds to fail, more than 10 times longer than a typo in the name itself.
We traced a real lookup from the root servers down. Here’s how DNS works, and why that typo crawled.
What is DNS?
DNS, the Domain Name System, is the internet’s address book. It turns a name you can remember, like droidcrunch.com, into the IP address a computer needs to connect, like 104.21.22.36.
Why not just use the numbers? Because they change. A site moves to a new host, its IP changes, and the name stays the same. DNS is the layer that lets that happen without anyone updating a bookmark.
It isn’t one big database either. It’s millions of servers, each responsible for a small slice of names, that point to each other. No single company runs it, and no single server knows every answer.
That design is why it scales to every domain on the internet. It’s also why a lookup takes a few hops.
How DNS works, step by step
When you type a domain into your browser, four kinds of servers can get involved:
- The recursive resolver. Your ISP’s server, or a public one like Cloudflare’s 1.1.1.1. It does the legwork for you and remembers answers.
- A root server. It doesn’t know where droidcrunch.com lives. It knows who runs “.com” and says “ask them”.
- The TLD server. The “.com” servers don’t know the IP either. They know which name servers hold the site’s records.
- The authoritative name server. It holds the real records and gives the final answer, plus a TTL that says how long anyone may cache it.
Your device only ever talks to the resolver. The resolver walks the chain, hands you the IP and keeps a copy, so the next person who asks gets it instantly.

That’s the textbook version. In practice, most of those hops never happen, which our trace showed.
We traced a real lookup for droidcrunch.com
We ran the lookup with dig, the standard DNS tool on Linux and Mac. Our test server’s network blocks direct DNS traffic on port 53, so every query went over DNS over HTTPS (dig’s +https option), which asks the same resolvers through an encrypted connection.
Here’s the plain question and answer:
$ dig +https @1.1.1.1 droidcrunch.com A
;; ANSWER SECTION:
droidcrunch.com. 300 IN A 104.21.22.36
droidcrunch.com. 300 IN A 172.67.202.60
;; Query time: 15 msec
;; SERVER: 1.1.1.1#443(1.1.1.1) (HTTPS)
Two A records, each valid for 300 seconds. The site sits behind Cloudflare, so both addresses belong to Cloudflare’s network rather than to the server that stores our files.
To see the chain behind that answer, we asked each level who it hands off to. Google’s resolver also reports which server gave it each answer:
| We asked | Answered by | What it said |
|---|---|---|
| Who runs the root zone? | b.root-servers.net | 13 root servers, a to m.root-servers.net |
| Who runs .com? | a.gtld-servers.net | 13 servers, a to m.gtld-servers.net |
| Who runs droidcrunch.com? | A Cloudflare name server | aria.ns.cloudflare.com and ned.ns.cloudflare.com |
| What’s the IP of droidcrunch.com? | A Cloudflare name server | 104.21.22.36 and 172.67.202.60, cache for 300 seconds |
Three hand-offs, then the answer. That’s the full walk a resolver makes when it has nothing cached.
Here’s the catch: it almost never has nothing cached. The root and .com answers stay valid for days, so a busy resolver already knows them. Our timing test further down shows what that does to speed.
What is a DNS server?
“DNS server” means any of the four machines above, but most people use it for the first one: the resolver your device asks.
Unless you’ve changed it, that’s whatever your Wi-Fi router hands out, which usually forwards to your internet provider. That default works. It’s also the one you know least about: how fast it is, whether it filters sites and what it logs.
Public resolvers are the alternative. The big three are Cloudflare (1.1.1.1), Google (8.8.8.8) and Quad9 (9.9.9.9), which also blocks domains known to spread malware.
Every query to a resolver shows which site you’re about to visit. Classic DNS sends it in plain text, so your provider can read the whole list. Encrypted DNS (DNS over HTTPS or DNS over TLS) hides it from the network, though the resolver still sees it.
A VPN normally sends your lookups through its own resolver. When it doesn’t, that’s a DNS leak, which our guide to how a VPN works explains.
Caching and TTL: why DNS changes take time
Every DNS answer comes with a TTL (time to live), a countdown in seconds. Until it hits zero, anyone who cached the answer reuses it without asking again.
Caches sit at several layers: your browser, your operating system, your router and the resolver. A lookup stops at the first layer that has a fresh copy.

Our records carry a 300-second TTL, so a change reaches most visitors within five minutes. Wikipedia surprised us. We asked 1.1.1.1 for it three times, five seconds apart, and got TTLs of 178, 27 and 64.
A countdown can’t go up, so those weren’t one cache. A big public resolver is many separate caches in many locations, each with its own copy of the answer. Which one you hit decides what you get.
That’s what “DNS propagation” really means. Nothing pushes your change out. Old copies expire one cache at a time.
Real-world tip: before you move a site to a new host, lower the A record’s TTL to 300 a day ahead. When you switch, the old address fades out in minutes instead of hours.
DNS records you’ll actually touch
A domain’s zone holds several record types. These are the ones you’ll meet when you set up a site or an email account, shown with what droidcrunch.com publishes:
| Record | What it does | On droidcrunch.com |
|---|---|---|
| A | Points the name at an IPv4 address | 104.21.22.36 and 172.67.202.60 |
| AAAA | Points the name at an IPv6 address | Two addresses starting 2606:4700 |
| CNAME | Makes one name an alias of another | None: www has its own A records |
| MX | Names the servers that accept your email | Two mail servers, priority 10 and 20 |
| TXT | Holds text, such as SPF and ownership checks | One SPF line and three verification codes |
| NS | Names the authoritative name servers | aria and ned.ns.cloudflare.com |
| SOA | Holds the zone’s admin details and timers | Primary server and refresh timers |
The A record is the one people mean when they say “point the domain at the server”. The AAAA record does the same for IPv6 addresses, which our IPv4 vs IPv6 guide explains.
The TXT records do more work than they look like they do. One of ours is the SPF line that tells inbox providers which services may send mail as droidcrunch.com. If your emails land in spam, check that first, then follow our SPF, DKIM and DMARC setup guide.
Should you switch DNS servers?
Only if you’ll notice the difference, and from a fast connection you might not. Here’s what three public resolvers did from our test server, which sits in a data center:
| Resolver | Cached name (median) | Brand-new name (median) | Slowest answer |
|---|---|---|---|
| Cloudflare 1.1.1.1 | 11 ms | 7 ms | 63 ms |
| Google 8.8.8.8 | 15 ms | 7 ms | 35 ms |
| Quad9 9.9.9.9 | 3 ms | 7 ms | 79 ms |
All three answered most questions in single-digit milliseconds. Quad9 was quickest on names it had cached, though it also gave the slowest single answer.
Look at the brand-new names. They weren’t slower, even though no resolver had seen them before. Each one already knew where droidcrunch.com’s name servers were, so only the last hop was new.
Don’t copy our winner. Resolvers answer from the location nearest to you, so your ranking depends on where you are and who your provider peers with. A 10-millisecond gap also only affects the lookup, which happens once per site before the page starts loading.
Switching is worth it for three reasons speed tests don’t show:
- Your provider’s resolver is slow or flaky. If sites sometimes hang on “Resolving host” before loading, that’s DNS.
- You want encrypted lookups. Most browsers can use encrypted DNS with Cloudflare, Google or Quad9 in a single setting.
- You want malware filtering. Quad9 refuses to answer for known bad domains.
Test from your own connection before you decide. This takes a minute:
# Mac or Linux: ask each resolver directly
dig @1.1.1.1 droidcrunch.com
dig @8.8.8.8 droidcrunch.com
dig @9.9.9.9 droidcrunch.com
# Windows (Command Prompt or PowerShell)
nslookup droidcrunch.com 1.1.1.1
nslookup droidcrunch.com 8.8.8.8
nslookup droidcrunch.com 9.9.9.9
Run each command a few times and compare the “Query time” lines, or the time Windows takes to answer. The first run can be slower, so judge the later ones.
When DNS breaks: what the errors mean
Most DNS errors say one of three things.
NXDOMAIN means the name doesn’t exist. Usually it’s a typo or a domain that expired.
Our two test typos showed how differently that can play out. A misspelled name, droidcrnch.com, came back NXDOMAIN in 15 to 35 milliseconds. The fake “.con” ending took 407 to 415 milliseconds on all three tries.
SERVFAIL means the resolver couldn’t get an answer. The site’s name servers may be down or misconfigured, or a security check (DNSSEC) failed.
A timeout means nothing answered at all. On your side, that’s usually your router or your resolver.
If you just changed name servers and the site works for some people but not others, wait. The .com servers’ own answers can take up to two days to expire everywhere.
Not every “can’t reach this site” error is DNS, though. If you see a 502 or 504 page, DNS already worked: your browser found the server and got a reply. Our 502 Bad Gateway guide covers what to fix there.
Where DNS fits when you set up a website
Buying a domain and buying hosting are two separate things, and DNS is what joins them. Our how web hosting works guide covers the hosting half.
You can connect them in one of two ways:
- Change the name servers to your host’s. The host then runs your whole DNS zone, and its setup screens fill in the records for you. Easiest for beginners.
- Keep the name servers and edit the A record to your host’s IP. More control, and your email records stay put.
Most hosts make the first option close to automatic. With Hostinger, a domain bought alongside the plan uses its name servers from the start, so there’s nothing to connect. Our Hostinger review covers what its plans include, and the current deals are in our Hostinger coupon codes roundup. (If you buy through our link, we may earn a commission at no cost to you.)
Common mistake: changing name servers on a live site without copying the old records first. Your website comes back, but your MX and TXT records don’t, and email quietly stops arriving.
Frequently asked questions
Is a domain name the same thing as DNS?
No. A domain name is the address you register, like droidcrunch.com. DNS is the system that stores what that name points to and answers questions about it. You rent the name from a registrar, while the records can live with your registrar, your host or a separate DNS provider such as Cloudflare.
Will changing my DNS server make downloads faster?
No. DNS only affects the moment your device looks up a site’s address, which usually takes a few milliseconds. Once the connection starts, your download speed depends on your internet plan, your Wi-Fi and the site’s server. A better resolver can stop pages hanging before they start, but it won’t raise your bandwidth.
Is it safe to use Google or Cloudflare DNS?
Yes, for most people. Both run huge, well-maintained networks and publish privacy policies on how long they keep query logs. The trade-off is trust: you’re moving the list of sites you visit from your internet provider to them. Quad9 is a non-profit option that also blocks known malware domains.
How do I flush my DNS cache?
On Windows, open Command Prompt and run ipconfig /flushdns. On a Mac, run sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder in Terminal. Chrome keeps its own cache, which you can clear at chrome://net-internals/#dns. Restarting your router clears its cache too.
What does ‘DNS server not responding’ mean?
Your device asked its resolver for an address and got no reply. The usual causes are a router that needs a restart, an internet provider’s resolver having an outage, or security software blocking DNS traffic. Restart the router first, then try setting 1.1.1.1 or 8.8.8.8 manually to see if the problem follows the resolver.
Is DNS encrypted?
Classic DNS isn’t. Queries travel in plain text on port 53, so anyone on the network path can read which sites you look up. DNS over HTTPS and DNS over TLS encrypt the query between you and the resolver. The resolver itself still sees every name you ask for, so pick one you trust.
Who controls DNS?
Nobody owns all of it. ICANN coordinates the root zone, 12 independent organisations run the 13 named root server identities, and each top-level domain has its own registry, such as Verisign for .com. Below that, every domain owner controls their own records through whichever DNS provider they choose.
How long does a DNS change take to work?
It depends on the TTL of the record you changed. An A record with a 300-second TTL updates for most visitors within five minutes. Changing name servers is slower, because the .com servers tell resolvers to cache that information for up to two days, so allow 24 to 48 hours.
The bottom line
DNS is the step before every website loads: a resolver turns a name into an IP address, walking from the root to the TLD to the site’s own name servers when it has to. In our trace it rarely had to, because caching answers most questions before they leave the first server.
That’s how DNS works in practice. Leave your DNS alone if sites load fine. Switch to a public DNS server if lookups hang or you want encryption and filtering, and test from your own connection first.
If you’re about to move a site, start with one thing: lower your TTL a day before the switch.



