You click a link, the tab spins, the status bar reads “Resolving host,” and for a second or two nothing happens before the page finally loads. That pause is a DNS lookup taking longer than it should — and it’s one of the most common, most overlooked causes of a connection that “feels slow” even when your actual internet speed tests perfectly fine. The good news is that DNS problems are also some of the fastest fixes on this list: most take under five minutes, and none require networking expertise.
Here’s what’s actually happening when DNS lags, and the fixes that work — in the order that gets you the biggest improvement fastest.
Quick Overview
To fix a slow DNS lookup, switch to a faster public DNS resolver — Cloudflare (1.1.1.1) or Google (8.8.8.8) — then flush your DNS cache and, if your browser supports it, enable DNS over HTTPS. These three changes alone resolve the vast majority of slow-lookup complaints. If pages still stall intermittently after that, the remaining culprit is usually an IPv6 timeout, a VPN routing DNS oddly, or a leftover virtual network adapter — not resolver speed itself.
What’s Actually Happening When DNS Is Slow
Every time you visit a site, your device has to translate the domain name into an IP address before it can connect — that translation step is the DNS lookup. A typical lookup takes somewhere between 20 and 120 milliseconds, fast enough to be invisible. When it drags into full seconds, one of a handful of things is usually responsible: a slow or overloaded resolver assigned by your ISP, a stale or bloated local cache, an outdated router adding latency to every device on your network, or a dual-stack IPv6/IPv4 timeout quietly adding delay in the background.
The High-Impact Fixes First
1. Switch to a faster public DNS resolver
This is the single highest-return change available. ISP-assigned resolvers are frequently the slowest link in the chain, while public resolvers like Cloudflare and Google use global Anycast routing so your query gets answered by the nearest available node rather than a single distant server. On Windows, this means opening your network adapter’s properties and manually entering the resolver addresses instead of leaving it on automatic. On Mac, the equivalent setting lives under System Settings, in your network’s DNS configuration. Android users get a shortcut version of this: enabling Private DNS locks in a fast, encrypted resolver across every network the device joins, rather than resetting it per-network.
2. Flush your DNS cache
Your operating system caches DNS responses so it doesn’t re-query for the same domain repeatedly — helpful when the cache is fresh, actively harmful when it’s stale or corrupted, since it can keep serving an outdated address long after the real one changed. On Windows, this is a single command (ipconfig /flushdns) in Command Prompt. Flushing is worth doing any time you switch DNS providers, notice intermittent slow loads, or migrate a site to a new server.
3. Don’t forget your browser’s separate cache
This is the step almost everyone misses: Chrome keeps its own DNS cache, entirely separate from the operating system’s. Flushing Windows or macOS doesn’t touch it. In Chrome, go to chrome://net-internals/#dns and click “Clear host cache.” If you’ve flushed the system cache and nothing changed, this is very often why.
4. Enable DNS over HTTPS (DoH)
DoH encrypts DNS queries and frequently routes them through faster paths than unencrypted lookups, while also preventing ISP-level interception that can slow resolution down. In Chrome, this lives under Settings → Privacy and Security → “Use secure DNS” — select Cloudflare or Google as the provider.
Fixing It Network-Wide Instead of Device-by-Device
Changing DNS settings on one laptop only fixes that laptop. If every device on your network is affected — phone, tablet, smart TV, game console — the more efficient fix is changing DNS at the router level. Log into your router’s admin panel (commonly at 192.168.1.1 or 192.168.0.1), find the DNS field under WAN, Internet, or DHCP settings, and enter a public resolver there instead. One catch worth knowing upfront: some ISP-provided routers lock this field, in which case you’re stuck setting DNS per-device or replacing the router.
While you’re in the router settings, a simple restart is also worth trying on its own — unplugging for about 30 seconds clears the router’s own DNS cache and resolves a surprising number of intermittent slowdowns without touching any settings at all. Outdated router firmware can independently add 50 to 200ms of latency to every query on the network, so checking for a firmware update is worth a few minutes if the problem persists after a DNS change.
The Less Obvious Culprit: IPv6
If lookups are fast most of the time but occasionally hang for a couple of seconds seemingly at random, IPv6 is a common hidden cause. On networks that don’t fully support it, dual-stack resolution sometimes attempts an IPv6 lookup first, waits for it to time out, and only then falls back to IPv4 — adding a delay that’s invisible until you disable IPv6 and notice pages resolving faster immediately. This is worth testing specifically if the standard resolver-and-cache fixes above didn’t fully resolve intermittent stalls.
For Website Owners, Not Just Everyday Browsing
If you’re troubleshooting this for your own site’s performance rather than your personal browsing, a couple of additional levers help specifically: self-hosting fonts and other external dependencies removes the extra DNS lookups those third-party requests trigger, and adding DNS prefetch hints for resources you can’t self-host lets the browser resolve those domains in the background before they’re actually needed — both directly improve Time to First Byte and perceived load speed for visitors.
Frequently Asked Questions
Is it safe to switch to Google or Cloudflare DNS?
Yes. Both are widely used, publish clear privacy policies, and switching only changes how domain names are translated to IP addresses — it doesn’t change what you can access or expose any additional data.
Does flushing DNS delete anything else, like passwords or history?
No. It only clears temporarily cached lookups. Browser history, saved passwords, and files are untouched.
What’s the average DNS lookup time supposed to be?
Roughly 20 to 120 milliseconds. Anything noticeably longer than that on a regular basis points to one of the causes covered above rather than normal network behavior.
Will changing DNS increase my internet speed?
Not bandwidth directly — DNS doesn’t affect how much data your connection can move. What it does affect is initial connection delay, which is often what makes browsing feel slow even on a fast connection.
I fixed my computer’s DNS, but pages are still slow on my phone — why?
Because a device-level DNS change only applies to that device. Fixing it network-wide requires changing the DNS setting at the router level, or configuring each device individually.
Final Verdict
Slow DNS lookup is one of the most overlooked causes of a connection that feels broken when it isn’t — and one of the fastest problems on this list to actually fix. Start with a resolver switch and a full cache flush (system and browser both), add DNS over HTTPS, and check IPv6 if intermittent stalls remain. For most people, the entire fix takes under ten minutes and doesn’t require any networking background at all.
