Few things test your patience like watching a browser sit on a spinning wheel while a page loads. More often than not, the culprit isn’t a slow connection — it’s a sluggish DNS lookup.

4 related posts

Slow DNS impact: Can add 5–15% to page load time ·
Fastest public DNS (Q4 2024): Cloudflare 1.1.1.1 (per DNSPerf (real-time DNS performance monitor)) ·
Typical browser connection count: 50–100 DNS lookups per page ·
Average lookup time: 20–50 ms for fast resolvers

Quick snapshot

1Confirmed facts
2What’s unclear
  • Exact impact of DNS on user experience varies by network and geography
  • Performance of public DNS servers can change due to routing updates
3Timeline signal
  • DNSPerf tests enterprise DNS providers every minute from 200+ global locations, providing real-time latency data
4What’s next
  • Encrypted DNS (DNS over HTTPS/TLS) is becoming the default on all major platforms, reducing spoofing risks (DNS Speed Test)
  • Browser-based test tools like DNS Speed Test let you find the fastest server for your location instantly

Here’s a quick reference on DNS basics and performance metrics.

Metric Value
What is DNS? Domain Name System converts human-readable names to IP addresses
Typical lookup time 20–50 ms for fast resolvers
Fastest public DNS (Q4 2024) 1.1.1.1 (Cloudflare) – reported ~11 ms median per DNSPerf
Common cause of slowness Overloaded ISP DNS servers or stale cache
Effect on browsing Each lookup adds latency; a slow DNS can double page load time

Why Is My DNS Lookup So Slow?

Network latency and ISP issues

  • Distance to your ISP’s DNS server and its current load directly affect response time. ISP defaults often run on older hardware with limited capacity.
  • According to Microsoft Q&A guidance, a slow name resolution is frequently caused by an overburdened local DNS service.

Expired or corrupted DNS cache

  • Your system stores recent lookups in a local cache, but stale entries can cause delays or failures. Flushing this cache is one of the fastest remedies.
  • Speedify’s support documentation notes that DNS leak protection features can also interfere with resolution speed on Windows.

Misconfigured local settings

  • Multiple active network adapters or incorrect Namespace Routing Policy (NRPT) entries can slow lookups. Windows Active Directory (community guide) recommends validating adapter configuration and rolling back changes if needed.
The upshot

The most common bottle-neck is not your internet speed — it’s the DNS server your device is talking to. Moving from an ISP default to a public resolver can cut lookup time by 50% or more.

The pattern: slow browsing often starts with slow name resolution, and the fix usually begins with switching servers or clearing cache.

How to Speed Up DNS Lookup?

Switch to a faster public DNS server

  • Replacing your ISP’s DNS with a public resolver is the single most effective change. Cloudflare 1.1.1.1, Google 8.8.8.8, Quad9 9.9.9.9, and OpenDNS 208.67.222.222 are all free.
  • Real-time benchmarks from DNSPerf show Cloudflare maintaining the lowest median latency across global tests.

Enable DNS caching and prefetching

  • Modern browsers and OSes cache DNS results automatically. Prefetching can pre-resolve links on the page, reducing wait time for subsequent clicks.
What to watch

Enabling DNS over HTTPS (DoH) in your browser or OS adds encryption, which can slightly increase latency per lookup but protects against spoofing — a worthwhile trade-off for most users.

The implication: a faster DNS server plus smart caching is the easiest performance win for everyday browsing.

How to Fix Slow DNS Lookup on Windows, macOS, and Android

Windows 10/11: Change DNS via Control Panel

  1. Go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active connection, select Properties, then double-click Internet Protocol Version 4 (TCP/IPv4) and choose Use the following DNS server addresses.
  2. Community guidance for Windows Active Directory recommends running the built-in Network Troubleshooter as a first diagnostic step.

macOS: Modify network settings

  1. Open Apple menu > System Settings > Network, select your service (Wi‑Fi or Ethernet), click Details, then choose DNS.
  2. Add your preferred DNS server addresses using the + button.
  3. This method works on macOS Sonoma 14 and Ventura 13, per Apple Support (official configuration guide).

Android: Use Private DNS mode

  1. Go to Settings > Connections > More connection settings > Private DNS.
  2. Select Private DNS provider hostname and enter one.one.one.one (Cloudflare) or dns.google.
  3. This encrypts all DNS queries and bypasses the ISP’s resolver.

Flush DNS cache on each platform

  1. Windows: Run ipconfig /flushdns in Command Prompt (Admin).
  2. macOS: Run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal.
  3. Android: Rebooting the device clears the cache, or toggle Airplane mode.
  4. Microsoft Q&A also mentions namebench as a utility to identify a faster DNS service for your region.
Why this matters

Flushing the DNS cache forces your device to query fresh records, eliminating any corrupted or stale entries that might be causing delays. It’s safe, takes seconds, and should be part of your regular maintenance.

Bottom line: Changing your DNS server to a fast public resolver like 1.1.1.1 or 8.8.8.8, combined with periodic cache flushing, cuts lookup time by more than half — and the setup takes just a few minutes per device.

What this means: with a few clicks or commands, you can bypass your ISP’s slow resolver and cut lookup time dramatically.

Is 1.1.1.1 or 8.8.8.8 Faster?

Three widely used public DNS resolvers, one key question: which delivers the lowest latency? The answer depends on location, but global benchmarks paint a clear picture.

Provider Primary IP Median Latency (Q4 2024) Privacy
Cloudflare 1.1.1.1 ~11 ms (per DNSPerf) Captures minimal data; no personal info stored
Google 8.8.8.8 ~20 ms (per DNSPerf) Retains usage data for up to 48 hours
Quad9 9.9.9.9 ~25 ms (industry benchmarks) Blocks malicious domains; logs limited
OpenDNS 208.67.222.222 ~30 ms (industry benchmarks) Offers filtering options; logs anonymized

Tier 1 sources like DNSPerf (real-time DNS performance monitor) and DNS Speed Test (location-aware benchmark tool) show that Cloudflare consistently wins on raw speed, though Google’s network size often gives it lower latency in regions where Cloudflare lacks edge nodes.

Upsides

  • Both Cloudflare and Google are free and globally distributed
  • Switch takes less than a minute and offers immediate speed improvement
  • Encrypted options (DoH/DoT) are available on both

Downsides

  • Privacy policies differ — Google logs more usage data than Cloudflare
  • Neither guarantees speed in all regions; a local benchmark is advised
  • Some corporate networks block public DNS, causing failure
Bottom line: While Cloudflare leads in global median latency, the fastest server for your location may differ — run a local benchmark before committing to a resolver.

The catch: raw speed isn’t everything — privacy, regional coverage, and network policies all factor into your choice.

How to Refresh DNS and Flush DNS Cache

Flush on Windows (ipconfig /flushdns)

  • Open Command Prompt as administrator and type ipconfig /flushdns. You should see “Successfully flushed the DNS Resolver Cache.”
  • According to Microsoft Q&A support, flushing forces the system to query fresh records and resolves most cache-related delays.

Flush on macOS (sudo dscacheutil -flushcache)

  • Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your admin password when prompted.
  • Apple Support (official configuration guide) confirms this command clears the local DNS cache.

Flush on Linux (systemd-resolve –flush-caches)

  • If using systemd-resolved, run sudo systemd-resolve --flush-caches. For other resolvers, use sudo service nscd restart or sudo dnsmasq -k -C /dev/null as appropriate.

Browser-specific cache clearing

  • Chrome: Go to chrome://net-internals/#dns and click “Clear host cache.”
  • Firefox: Type about:networking#dns and click “Clear DNS Cache.”
  • Browser DNS cache is separate from OS cache — flushing both ensures a completely fresh lookup path.
The catch

Flushing the DNS cache temporarily increases lookup load for the next few requests, but the long-term benefit of removing stale entries far outweighs this brief overhead.

Bottom line: Flushing the DNS cache is a zero-risk operation that eliminates staleness on all platforms, and should be part of any troubleshooting workflow.

The takeaway: clearing both OS and browser caches ensures no stale records remain, giving you a clean state for fresh lookups.

Common DNS Issues and How to Fix Them

DNS lookup fails entirely

  • This often stems from a server outage, incorrect network configuration, or firewall blocking DNS. Run the built-in Network Troubleshooter (Windows) or check your router’s DNS settings.
  • Community discussions on Reddit recommend rebooting the router as a first step when the DNS server is not responding.

Slow DNS resolution due to server overload

DNS poisoning or spoofing

  • Using DNSSEC-enabled resolvers (such as Quad9) and enabling DNS over HTTPS can reduce the risk of man-in-the-middle attacks.

Incorrect DNS record types (A vs AAAA)

  • If your application requests an IPv6 record but your network only supports IPv4, the lookup will time out. Configure your OS to prefer IPv4 if you experience consistent delays.

“If your DNS resolution is terribly slow, trying a faster DNS service is the logical first step.”

— Microsoft Q&A support (official Microsoft answers forum)

“DNS settings on Mac are changed via Apple menu > System Settings > Network > service > Details > DNS.”

— Apple Support (official configuration guide)

The implication: whether you’re on Windows, macOS, or Android, a fast public resolver and a fresh cache are your two most reliable levers. ISP defaults will never match the uptime and speed of dedicated DNS providers like Cloudflare or Google.

Additional sources

discussions.apple.com, youtube.com, youtube.com, forums.grc.com, youtube.com

Don't miss these

Frequently asked questions

How do I know if my DNS is slow?

Run a DNS benchmark tool like DNS Speed Test or DNSPerf. Compare your current resolver’s response time to public options. Anything above 100 ms is slow.

Can changing DNS server speed up my internet?

Yes. Since DNS lookup is part of every page request, a faster resolver reduces the time before the browser can start downloading content. The improvement is most noticeable on sites with many third-party resources.

Is DNS caching safe?

Yes. DNS caching is a standard performance feature. The cache only holds records for a limited time (TTL), and flushing it clears stale data without harming your system.

Will flushing DNS harm my computer?

No. Flushing the DNS cache is a safe operation that removes temporary lookup records. The system will re‑query the DNS server the next time it needs those records, which may add a slight delay initially.

Does DNS affect ping in gaming?

DNS lookup is performed once when connecting to a server. After the initial connection, game traffic uses the direct IP, so DNS speed has minimal impact on in‑game latency. However, a slow DNS can delay the initial server search.

What is the best DNS server for speed in 2025?

Based on current DNSPerf data, Cloudflare 1.1.1.1 leads with the lowest median latency. Google 8.8.8.8 and Quad9 9.9.9.9 are close seconds. Run a local speed test to confirm which performs best from your location.

For home users and IT admins alike, the path to faster DNS is clear: benchmark your current performance, switch to a tested public resolver, and keep your cache clean. A few minutes of configuration can shave seconds off every page load — and that adds up to real time saved every day. Check your broadband speed to confirm your improvements, and explore travel deal tips while your connection flies.