Few things kill a browsing session faster than waiting for a page that refuses to load — only to watch the address bar spin for 11 seconds before giving up. That lag is almost always DNS-related, and unlike your internet speed, it’s fixable in minutes once you know where to look. This guide covers the fastest cross-platform fixes for slow DNS lookups on Windows, Android, and beyond, backed by Microsoft docs, specialist benchmarks, and real-world test data.
Google DNS: 8.8.8.8 · Cloudflare DNS: 1.1.1.1 · OpenDNS: 208.67.222.222 · Ideal lookup time: <20ms · Common delay: 11s reported
Quick snapshot
- Flush DNS cache — resolves corrupted entries
- Switch to 1.1.1.1 or 8.8.8.8 — faster servers
- Disable IPv6 — can cause resolution delays
- Run ipconfig /flushdns
- Change adapter DNS properties
- Test with Resolve-DnsName
- Set Private DNS hostname
- Clear app cache
- Reset network if needed
- ping — basic reachability
- dig — DNS query details
- DNSPerf — global server rankings
| DNS Server | Primary IP | Secondary IP | Best For |
|---|---|---|---|
| Google Public DNS | 8.8.8.8 | 8.8.4.4 | Reliable global coverage |
| Cloudflare DNS | 1.1.1.1 | 1.0.0.1 | Speed and privacy |
| Control D DNS | 76.76.2.1 | 76.76.10.1 | Gaming, reliability |
| OpenDNS | 208.67.222.222 | 208.67.220.220 | Security filtering |
| Quad9 DNS | 9.9.9.9 | — | Malware blocking |
| Surfshark DNS | 194.169.169.169 | — | Gaming consoles |
What is slow DNS lookup?
DNS (Domain Name System) is the phonebook of the internet — it translates human-readable domain names like example.com into IP addresses that computers use to communicate. When this translation stalls, every connection request downstream gets held up, making even fast connections feel sluggish.
DNS lookup process
The DNS resolution chain follows a predictable path: your device queries its local cache first, then asks your configured DNS server, which in turn queries root and TLD servers before returning the final IP address. Each hop adds latency, and bottlenecks anywhere in this chain manifest as slow DNS lookups.
DNS lookup times above 100ms indicate a slow DNS server, according to DNSRobot diagnostics. Anything under 20ms is considered fast for most users.
Normal vs slow times
Under normal conditions, a DNS lookup completes in milliseconds. Users on Windows have reported name resolution taking roughly 11 seconds, which Microsoft Q&A community posts attribute to specific Windows name resolution bugs — far outside any acceptable range.
Why is my DNS lookup so slow?
Slow DNS lookups stem from three main categories: server-side problems, local cache corruption, and network configuration issues.
Server issues
Your ISP’s DNS servers may be overloaded, geographically distant, or simply poorly maintained. Switching to a public alternative like 8.8.8.8 or 1.1.1.1 often eliminates this bottleneck entirely, with Cloudflare maintaining notably lower latency globally.
Cache problems
Both operating systems and browsers maintain local DNS caches to avoid repeat lookups. When these caches accumulate corrupted or outdated entries, subsequent resolutions can fail or hang. Flushing the cache clears these problematic records and forces fresh lookups from your configured DNS server.
Network factors
- IPv6 misconfiguration can cause resolution delays when networks don’t handle it properly
- Virtual network adapters (VPN software, hypervisors) can conflict with DNS routing
- Routers with built-in DNS proxy features may introduce unnecessary hops
DNS issues become more pronounced on mobile networks, where base latency is already higher. Android’s Private DNS setting applies across both Wi-Fi and cellular connections.
How to fix slow DNS lookups?
The fixes below work across platforms. For detailed platform steps, skip to the Windows section or Android section.
Change DNS servers
Switching to faster DNS servers is the most impactful change. Google’s Public DNS (8.8.8.8 / 8.8.4.4) and Cloudflare DNS (1.1.1.1 / 1.0.0.1) are widely available, well-maintained, and typically outperform ISP defaults. OpenDNS (208.67.222.222) adds security filtering for phishing domains.
Flush DNS cache
This clears locally stored DNS records that may be stale or corrupted. On Windows, run Command Prompt as administrator and execute ipconfig /flushdns. On Android, clear individual app caches or reset network settings entirely.
Test with tools
Before and after changes, measure your lookup time using nslookup -debug domain.com in Command Prompt. Chrome DevTools (F12 → Network → Hard Reload) shows exact DNS Lookup timing in the Timing tab. DNSPerf maintains real-time rankings of DNS server performance.
Cloudflare DNS offers very low latency, excellent reliability, and strong privacy with no logs. For users concerned about logging practices, Google Public DNS records IP address, ISP info, and location — a meaningful difference if privacy is a priority.
How to fix slow DNS lookup on Windows?
Windows offers multiple paths to change DNS settings, depending on whether you prefer the Settings app or command-line tools.
Windows 10/11 steps
- Open Settings → Network & Internet
- Click Change adapter options
- Right-click your active adapter and select Properties
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties
- Choose “Use the following DNS server addresses”
- Enter your preferred DNS (e.g., 8.8.8.8 for Google) and alternate (8.8.4.4)
- Click OK, then close all windows
Windows 7 steps
Windows 7 uses the classic Network and Sharing Center: Control Panel → Network and Sharing Center → Change adapter settings → right-click adapter → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties. The DNS entry fields are identical to Windows 10/11.
PowerShell tests
PowerShell’s Resolve-DnsName command provides detailed diagnostics:
- Resolve-DnsName google.com — basic lookup
- Resolve-DnsName google.com -Type A -DnsOnly — specific record type
- Measure-command {Resolve-DnsName google.com} — measure resolution time
Gaming-focused DNS picks like Control D (76.76.2.1) are optimized for low latency and reliability, but standard browsing DNS choices like Google or Cloudflare prioritize broad coverage. For competitive gaming, the difference matters; for casual browsing, either works.
Best DNS servers for speed?
Speed rankings vary by use case. Gaming, security, and privacy each have different winners.
1.1.1.1 vs 8.8.8.8
Cloudflare DNS ranks high for pure speed but has lower malware blocking compared to security-focused alternatives. Google Public DNS offers broad global infrastructure but logs IP addresses, ISP info, and location, per Control D’s comparison. If privacy matters more than malware filtering, Cloudflare wins; if you want maximum coverage without configuration, Google is the safer default.
Gaming options
Control D (76.76.2.1) ranks as the overall best DNS for gaming due to low latency and rock-solid reliability, according to Control D’s 2026 benchmarks. For Android gaming specifically, top choices are Cloudflare, Google Public DNS, and Surfshark due to speed and reliability, per Surfshark’s testing. Caasify DNS achieves up to 30% lower latency than Google or OpenDNS in high-congestion regions, though it’s less widely deployed. If you’re experiencing slow DNS lookups, you can learn how to address them by visiting Descale your Nespresso Vertuo.
Security picks
Quad9 (9.9.9.9) focuses on security with low latency by blocking malware domains. OpenDNS (208.67.222.222) adds phishing block and security filtering, making it popular for business networks. NextDNS offers highly customizable configuration with AI threat detection for users who want granular control.
Gcore DNS has high uptime but performs nearly twice as slow as competitors, according to Control D benchmarks. For most users, that trade-off isn’t worth the uptime guarantee.
Best DNS servers for gaming — comparison
Six services, three trade-offs: latency, privacy, and security features don’t come together in one package.
| DNS Service | Primary IP | Latency | Privacy | Security |
|---|---|---|---|---|
| Control D | 76.76.2.1 | Lowest | Full control | Custom |
| Cloudflare | 1.1.1.1 | Very low | No logs | Basic |
| 8.8.8.8 | Low | Logs data | None | |
| OpenDNS | 208.67.222.222 | Low | Moderate | Phishing block |
| Quad9 | 9.9.9.9 | Low | Moderate | Malware block |
| Caasify | Varies | 30% lower in congestion | Moderate | None |
The pattern is clear: no single DNS server wins on all three metrics. Gaming prioritizes latency; privacy advocates prefer no-log providers; security-conscious users need malware blocking. Pick based on your primary concern, not a one-size-fits-all recommendation.
Pros and cons of switching DNS
Upsides
- Faster page loads when DNS is the bottleneck
- Improved privacy (Cloudflare, Control D don’t log IP data)
- Security filtering blocks known malicious domains
- Works across all apps without per-app configuration
- Free for public DNS services with global infrastructure
Downsides
- Some corporate networks block external DNS for security policies
- Changing DNS doesn’t fix speed issues from slow internet connections
- Security-focused DNS may occasionally block legitimate sites
- Custom DNS can interfere with parental control software
- Router-level DNS changes affect all devices but require more configuration
Step-by-step DNS troubleshooting checklist
Quick wins (do first)
- Run ipconfig /flushdns in Windows Command Prompt (admin)
- Try a different browser (Chrome, Firefox, Edge)
- Restart your router and device
- Disable VPN software temporarily
Diagnostic steps
- Use nslookup -debug domain.com to measure lookup time
- Test with Resolve-DnsName in PowerShell
- Check DNSPerf for your region’s DNS server performance
- Compare times with 8.8.8.8 vs your current DNS
Configuration changes
- Switch to Cloudflare (1.1.1.1) or Google (8.8.8.8) as primary DNS
- On Android 9+, set Private DNS to dns.google or 1dot1dot1dot1.cloudflare-dns.com
- Consider Control D (76.76.2.1) for gaming, Quad9 for security filtering
- Set up local DNS resolver like Unbound for system-level caching
DNS issues are more visible on mobile networks where base latency is already higher. After any DNS change, test on both Wi-Fi and cellular to confirm improvements are consistent.
Confirmed facts and common uncertainties
Confirmed
- Public DNS servers 8.8.8.8, 1.1.1.1, 76.76.2.1 are valid and widely supported
- Flushing DNS cache resolves most clogs from corrupted entries
- Android Private DNS works across Wi-Fi and cellular (Android 9+)
- Control D ranks highest for gaming latency in 2026 benchmarks
- DNSRobot diagnostics confirm 100ms+ indicates a slow server
Unclear
- Precise regional latency benchmarks vary across sources without standardized test methodology
- Specific reasons some networks block 1.1.1.1 DNS vary by ISP and region
- Long-term privacy implications of Google DNS logging haven’t been audited publicly
Control D strikes the perfect balance between low latency, rock-solid reliability, and full privacy control.
— Control D, DNS Provider (Gaming DNS Rankings)
In a real-world ping test, gamers using Caasify DNS were able to achieve up to 30% lower latency compared to Google DNS.
— Caasify, DNS Provider (Latency Benchmarks)
Slow DNS lookups aren’t a mystery — they’re a solvable configuration problem. For most users, switching to Cloudflare (1.1.1.1) or Google DNS (8.8.8.8) and flushing the cache eliminates the issue within minutes. For gamers, Control D (76.76.2.1) offers measurably lower latency at the cost of broader coverage. The fix is free, takes under 10 minutes to implement, and the performance difference is immediate.
Related reading: Telstra Speed Test · HP Warranty Check
mozedia.com, youtube.com, surfshark.com, dnsrobot.net, pinggy.io, learn.microsoft.com, youtube.com
While these steps target Windows and Android, the Norwegian slow DNS lookup guide provides comparable techniques like switching to 1.1.1.1 for quicker resolutions.
Frequently asked questions
What causes DNS errors?
DNS errors typically stem from misconfigured DNS settings, corrupted local caches, overloaded ISP DNS servers, or IPv6 conflicts. Outdated routers with poor DNS proxy implementations can also introduce failures.
How do I test DNS lookup time?
Run nslookup -debug domain.com in Command Prompt to see detailed resolution steps and timing. On Windows PowerShell, use Resolve-DnsName with Measure-Command to time the operation. Chrome DevTools (F12 → Network tab → hard reload) shows DNS Lookup time in the Timing panel for any page resource.
Is IPv6 causing slow DNS?
IPv6 misconfiguration can cause DNS resolution delays on some networks, particularly when routers or ISPs handle AAAA records poorly. If you experience slow lookups after enabling IPv6, disabling it temporarily via network adapter properties can help diagnose the issue.
What is DNSPerf?
DNSPerf is a global DNS performance monitoring service that ranks DNS servers by uptime and response time from multiple geographic regions. It’s useful for comparing providers before committing to a change.
Does router DNS matter?
Yes, if your router runs a DNS proxy or caching feature, it can add latency or serve stale records. Changing your router’s DNS settings (under LAN or DHCP configuration) applies the fix to all connected devices automatically.
Why clear DNS cache?
Clearing DNS cache removes stale, corrupted, or outdated records that can cause failed or slow resolutions. It forces fresh lookups from your configured DNS server, which is essential after switching DNS providers or troubleshooting resolution failures.
Ethan Cooper is Senior Reporter at Oz Reviewly, covering breaking stories and explainers.