Published Apr 8, 2026, 10:30 AM EDT
Roine Bertelson is a Stockholm-based tech writer, translator, and digital strategist with more than twenty years of hands-on experience in AI tools, Linux, consumer tech, cybersecurity, and SEO-driven content. He's known for turning complex topics into clear and practical guidance that helps readers solve real problems. People trust his work because he actually uses and tests the tools he writes about, breaks things on purpose, and translates the chaos of modern technology into advice that feels human, honest, and useful.
My speed tests came back smug and green. Downloads were fast. YouTube didn’t buffer unless I actively tried to break it. On paper, my connection looked like something you’d brag about in a Reddit thread. And still … every time I opened a page, there it was. That tiny, irritating pause. No loading bar, no spinner, and no reassuring flicker of activity. Just a weird half-second of nothing, like the internet had to gather itself before committing. It wasn’t long enough to complain about, but it was absolutely long enough to feel.
That kind of delay doesn’t show up in benchmarks. It lives somewhere else. In muscle memory, in expectation, and that subtle “why does this feel off?” that creeps in after the hundredth tab. I did what everyone does. Blamed the browser. I closed and reopened tabs. Considered blaming Vivaldi again because it’s always a little guilty of something. But this wasn’t RAM, it wasn’t the CPU, or even the connection itself. It was DNS quietly dragging its feet before anything else even had a chance to begin.
Why everything felt slow before it actually started loading
That invisible delay wasn’t bandwidth, it was lookup time
Before a website loads, your system has to ask a very basic question: where is this thing? That question goes to a DNS resolver. It translates something human, like a domain name, into something your system can actually connect to. And nothing happens until that question gets answered. No content starts loading, no scripts spin up, and no images appear. Everything sits there, politely waiting for DNS to finish its job.
If that step is even slightly slow, the whole experience feels hesitant. Not broken, just … unsure. Most Linux systems, including Mint and Ubuntu-based setups, default to whatever DNS your ISP hands out. It works in the same way as a slightly dented shopping cart still rolls.
But those servers aren’t always fast. They’re not always close. And they’re very rarely optimized for responsiveness in the way modern public resolvers are. So every new request carries a bit of hesitation baked into it. Not enough to scream, but enough to sigh.
Quiz
8 Questions · Test Your Knowledge
The MUO DNS & Networking Challenge
Think you know why the internet hesitates? Put your DNS and networking knowledge to the ultimate test.
DNSNetworkingProtocolsSecurityPerformance
Begin
What does DNS stand for?
AData Network ServiceBDynamic Name SystemCDomain Name SystemDDigital Node Server
Correct! DNS stands for Domain Name System. It acts like the internet's phone book, translating human-friendly domain names like 'google.com' into machine-readable IP addresses so your browser knows where to connect.
Not quite — the answer is Domain Name System. DNS is the backbone of how we navigate the web without memorizing strings of numbers like 192.168.1.1 for every site we visit.
Continue
What is the term for the delay caused when your computer has to look up a domain name before loading a website?
ALatency spikeBDNS lookup timeCPacket lossDHandshake delay
Correct! DNS lookup time is the delay your device experiences while querying a DNS server to resolve a domain name into an IP address. Switching to a faster DNS provider like Cloudflare (1.1.1.1) or Google (8.8.8.8) can significantly reduce this pause.
Not quite — the answer is DNS lookup time. This is the specific delay caused by the name resolution process. While latency and packet loss are real networking issues, they describe different problems than the initial domain lookup pause.
Continue
Which of the following is Cloudflare's primary public DNS resolver IP address?
A8.8.8.8B9.9.9.9C1.1.1.1D208.67.222.222
Correct! Cloudflare's primary DNS resolver is 1.1.1.1, launched in 2018 with a focus on privacy and speed. It consistently ranks among the fastest DNS resolvers in the world and does not log your query data for advertising purposes.
Not quite — the correct answer is 1.1.1.1, which belongs to Cloudflare. For the record, 8.8.8.8 is Google's DNS, 9.9.9.9 is Quad9, and 208.67.222.222 is OpenDNS — all legitimate alternatives to your ISP's default DNS.
Continue
Which port does standard, unencrypted DNS traffic typically use?
APort 80BPort 443CPort 25DPort 53
Correct! DNS operates on port 53 by default and uses both UDP for quick queries and TCP for larger responses or zone transfers. This is one of the most fundamental port numbers in networking and appears frequently in firewall and security configurations.
Not quite — DNS uses port 53. Port 80 is HTTP, port 443 is HTTPS, and port 25 is SMTP for email. Knowing these standard port assignments is essential for anyone configuring firewalls or troubleshooting network issues.
Continue
What type of attack involves corrupting a DNS resolver's cache to redirect users to malicious websites?
ADNS tunnelingBDNS spoofingCARP poisoningDBGP hijacking
Correct! DNS spoofing, also called DNS cache poisoning, involves injecting false DNS records into a resolver's cache so that users are redirected to attacker-controlled sites without knowing it. DNSSEC (DNS Security Extensions) was developed specifically to help defend against this threat.
Not quite — the answer is DNS spoofing (or cache poisoning). DNS tunneling uses DNS queries to smuggle data, ARP poisoning targets local network traffic, and BGP hijacking affects internet routing at a much larger scale. Cache poisoning is the attack specifically targeting the DNS resolution process.
Continue
What is a DNS TTL value used for?
AIt sets the maximum number of hops a DNS packet can travelBIt defines how long a DNS record is cached before being refreshedCIt limits the number of simultaneous DNS queries a server can handleDIt encrypts the DNS response between server and client
Correct! TTL stands for Time To Live, and in DNS it specifies how many seconds a resolved record should be stored in cache before the resolver must query again. A low TTL means faster propagation of changes; a high TTL reduces DNS query load but slows updates.
Not quite — TTL in DNS defines the cache lifetime of a record, not hops, query limits, or encryption. Interestingly, IP packets also have a TTL field but it counts network hops, which is a common source of confusion since the same term means something different in each context.
Continue
Which type of DNS record is responsible for mapping a domain name to an IPv6 address?
AA recordBCNAME recordCAAAA recordDMX record
Correct! The AAAA record (pronounced 'quad-A') maps a domain name to a 128-bit IPv6 address. The standard A record handles IPv4 addresses, while CNAME is an alias record and MX records direct email traffic to the appropriate mail servers.
Not quite — IPv6 addresses are stored in AAAA records. The A record handles IPv4, CNAME creates domain aliases, and MX records handle mail routing. As IPv6 adoption grows, AAAA records are becoming increasingly important in DNS configurations.
Continue
In the original 1983 DNS specification (RFC 882), what was used to resolve hostnames before DNS existed and is still present on every modern operating system?
AWINS (Windows Internet Name Service)BThe HOSTS fileCNIS (Network Information Service)DNetBIOS broadcasts
Correct! Before DNS, a centrally maintained HOSTS.TXT file was distributed to every computer on the ARPANET. Your OS still checks the local hosts file (located at /etc/hosts on Linux/Mac or C:\Windows\System32\drivers\etc\hosts on Windows) before querying DNS — which is why it can be used to block websites or override DNS locally.
Not quite — the answer is the HOSTS file, a flat text file that predates DNS entirely. It's still checked first during name resolution on every modern OS, which is why malware sometimes modifies it to hijack traffic, and why savvy users edit it to block ads or override specific domains without touching DNS settings.
See My Score
Challenge Complete
Your Score
/ 8
Thanks for playing!
Try Again
The moment it clicked
Fast internet with slow starts is a very specific kind of annoying
What finally tipped me over wasn’t a failure. It was consistency. Once a page started loading, it flew. No complaints. No lag. It snapped into place as if everything were working perfectly. But getting to that point felt like knocking on a door and waiting just a little too long for someone to answer. So I started paying attention in a slightly obsessive way. Opened the same sites repeatedly. Compared the first loads with refreshes. Watched how cached pages behaved versus new requests.
Cached pages were instant. Like, aggressively instant. Fresh requests? That same awkward pause, every time. That’s when it stopped being a vague annoyance and started looking like a pattern. And DNS fits that pattern perfectly. Once I saw it, I couldn’t unsee it. Every click felt like it had to clear its throat first.
Switching DNS removed the hesitation instantly
A better resolver didn’t make things faster, it made them feel right
I switched away from my ISP’s DNS and tested a few well-known public resolvers:
- Cloudflare (1.1.1.1)
- Google DNS (8.8.8.8)
- Quad9 (9.9.9.9)
No big ceremony. No system overhaul. Just a quiet change in network settings and a reconnect. And the difference was immediate in a way that’s almost annoying. Pages didn’t pause anymore. They just opened. New tabs stopped feeling like a negotiation. Links responded the moment I clicked them. That weird micro-delay that had been quietly living in every interaction just disappeared. Same system, same browser, same everything.
But the entire experience felt tighter. More confident. Like the internet had finally decided to stop hesitating. It’s one of those changes that doesn’t show up dramatically anywhere, but once you notice it, going back feels like your system has suddenly developed commitment issues.
Journald made the behavior impossible to ignore
Watching DNS queries in real time turns a feeling into proof
At this point, I didn’t just want to feel the improvement. I wanted to catch it in the act. So I turned to journald, because if something is happening on a Linux system, it’s usually talking about it somewhere.
On systems using systemd-resolved, you can watch DNS queries live:
journalctl -u systemd-resolved -f Before switching DNS, the pattern was clear. Queries would come in, pause briefly, then resolve. Nothing dramatic, just slightly sluggish responses stacking up over time. After the switch, everything tightened. Requests are resolved faster, with fewer weird delays and less back-and-forth. It looked cleaner, more decisive, like the system wasn’t second-guessing itself anymore. And that’s a very satisfying part.
This wasn’t one of those tweaks where you convince yourself it feels better. The logs backed it up. The behavior changed in a way you could actually observe. That made the whole thing feel less like tweaking and more like fixing something that should never have been that slow to begin with.
Related
Router vs. Computer DNS Settings: Here's What Was Faster
Comparing DNS at the router versus PC level led to real improvements in my network’s speed and performance.
Removing friction beats chasing raw speed every single time
This isn’t about maxing out your connection. Your download speeds won’t suddenly double. Your speed test results won’t turn into bragging rights. Nothing about your bandwidth changes. What changes is how everything starts. And that’s where most of the experience lives. We don’t spend our days downloading massive files. We click. We browse. We jump between tabs. We follow links faster than we consciously think about them.
If every one of those actions has even a small delay before it begins, it adds up in a way that feels heavier than it should. It’s not dramatic. It’s not measurable in a way most tools care about. But it absolutely affects how your system feels. Switching DNS removes that hesitation. It makes everything feel immediate again. Responsive. Predictable. And once that friction is gone, it’s very hard to tolerate its return. Because now you know it was never your internet being slow. It was just waiting for someone else to answer a very simple question.