How to Fix Slow DNS Lookup: Windows, Mac, Router Fixes

You upgraded your internet plan, yet pages still stall. The culprit is often hiding in plain sight: slow DNS resolution. When your computer has to ask a server “where does example.com live?” dozens of times per session, those milliseconds add up. Microsoft reports average DNS lookup times of up to 11 seconds on some systems, turning what should be a seamless browse into an exercise in patience. The good news: with a few targeted commands and the right resolver, you can typically cut that delay down to under a second.

Typical slow lookup time: up to 11 seconds · Common fix: clear cache resolves clogged caches · Benchmark tool: DNSPerf or dig · PowerShell test: Measure-Command { Resolve-DnsName google.com } · Cloudflare DNS: 1.1.1.1

The table below consolidates the most frequently cited DNS performance figures and provider details from authoritative sources.

What is slow DNS lookup?

DNS (Domain Name System) acts as the internet’s phone book—your device asks a resolver to translate human-readable domains like google.com into IP addresses. When that lookup drags, every new site visit adds latency before the connection even starts. Microsoft documentation notes that name resolution slowness can reach approximately 11 seconds on affected systems, a delay invisible until you notice your browser twiddling its thumbs between page loads. The problem typically traces to outdated server addresses cached on your machine, ISP DNS servers that are geographically distant or overloaded, or local cache entries that have gone stale without your knowledge.

Causes of slow DNS

Community reports indicate several recurring culprits. ISP-provided DNS servers are frequently the first suspect—sometimes these servers route traffic through roundabout paths or simply experience high query loads. Outdated DNS server addresses stored on your computer after a previous network configuration can persist long after the original server has changed or become unavailable. High network latency between your location and your DNS resolver adds millseconds per query, and when multiplied across dozens of lookups per browsing session, the cumulative effect becomes noticeable. Router-level DNS settings inherited from older firmware configurations may also point to slow or defunct servers that your devices blindly trust.

Impact on browsing

When DNS resolution lags, the ripple effect touches every aspect of web performance. Initial page loads stall while the browser awaits an IP address before initiating any connection. Subsequent navigations to new domains repeat the same delay, compounding frustration on sites with multiple third-party resources. Streaming buffers may initialize slowly, and real-time applications that constantly resolve new endpoints suffer disproportionately. Microsoft Support documentation recommends testing name resolution with other devices to isolate whether DNS is the bottleneck or if broader network issues are at play.

How to fix slow DNS lookups?

The fastest path to resolution involves two parallel approaches: clearing cached data and switching to a faster public resolver. DNSPerf, which benchmarks A record lookups for apex domains from more than 200 worldwide locations, provides one of the most comprehensive views of how major resolvers perform globally. Switching from your ISP’s default DNS to a well-maintained public option like Cloudflare (1.1.1.1) or Google Public DNS (8.8.8.8) frequently slashes lookup times, according to community reports on Windows Forum.

Clear DNS cache

• Open an elevated Command Prompt (Windows) or Terminal (Mac)
• Run the appropriate flush command for your operating system
• Restart your browser and test with a site you haven’t visited recently

Flush DNS commands

For Windows, the command ipconfig /flushdns clears the resolver cache in an elevated Command Prompt window. Community tutorials recommend following this with ipconfig /renew to obtain a fresh DHCP lease and updated DNS assignments. On Mac systems, sudo dscacheutil -flushcache serves the same purpose according to Airtalk Wireless. Modern macOS versions also support sudo killall -HUP mDNSResponder, which restarts the mDNSResponder daemon responsible for local name resolution.

Change DNS servers

Changing your DNS servers involves updating either your operating system’s network settings or your router’s configuration to point to faster resolvers. Cloudflare’s 1.1.1.1 resolver uses the IP address 1.1.1.1, while Google’s alternative responds at 8.8.8.8—both are publicly documented and widely available. For Mac, navigate to System Settings > Network > Details > DNS and add your preferred servers. For Windows, access Network & Internet settings and modify the DNS configuration for your active adapter. Router changes vary by model, but most allow DNS server assignment in the WAN or LAN settings panel.

Use ping and traceroute

Before changing DNS settings, diagnose whether the problem originates with name resolution or your broader network connection. Running ping 8.8.8.8 tests basic connectivity, while ping google.com reveals whether DNS resolution specifically is slow. A traceroute to an IP address versus a domain name isolates the issue—if pinging by IP works smoothly but domain names lag, DNS is the likely bottleneck. Tom’s Hardware forums recommend ping -t 8.8.8.8 for Windows to run a continuous ping test and watch for packet loss that might indicate router-level problems.

DNSPerf tools

DNSPerf provides analytics from millions of real-user tests, making it a reliable source for comparing resolver performance across different regions and time periods. The service tests A record lookups for apex domains from more than 200 worldwide locations, offering both current benchmark data and historical trends with 30-day retention. According to DNSPerf’s methodology documentation, these benchmarks help identify which providers consistently deliver low latency for users in specific geographic areas. For enterprise users or anyone experiencing persistent slowness despite local fixes, DNSPerf data can guide resolver selection.

How to fix slow DNS lookup Windows 10?

Windows 10 users have multiple built-in tools for diagnosing and fixing DNS issues without installing additional software. Microsoft’s official Q&A documentation provides step-by-step guidance for resolving name resolution problems that reportedly reach 11 seconds on some configurations. The process typically involves running PowerShell commands to test current resolution performance, flushing the local DNS cache, and optionally modifying network adapter settings to use faster public DNS servers.

Windows troubleshooting

• Open PowerShell as Administrator
• Test current DNS resolution: Measure-Command { Resolve-DnsName google.com }
• Flush the cache: ipconfig /flushdns
• Renew DHCP lease: ipconfig /renew
• Change DNS servers in Network Settings if needed

PowerShell DNS test

PowerShell’s Resolve-DnsName cmdlet provides a straightforward way to measure how long your current DNS configuration takes to resolve a domain. Running Measure-Command { Resolve-DnsName google.com } outputs the elapsed time in milliseconds, giving you a baseline before making changes. Compare results before and after flushing your cache or switching servers to quantify the improvement. Microsoft documentation notes that namebench (owned by Google) hunts down the fastest DNS servers available for your computer based on local analysis, and it works across Windows, Mac, and UNIX systems.

The implication: PowerShell gives you measurable proof that your fix actually worked—before versus after numbers beat guesswork.

How to fix slow DNS lookup Mac?

Mac systems handle DNS caching and resolution differently than Windows, but the underlying principles remain the same. Apple Communities discussions from long-standing threads document multiple approaches that users have found effective for resolving slow wireless DNS lookups, including disabling IPv6 and switching to alternative DNS providers. The macOS network stack relies on the mDNSResponder process, which can be restarted without a full system reboot.

Mac-specific commands

For macOS, the primary cache flush command is sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder. On older macOS versions, sudo discoveryutil mdnsflushcache served this purpose. According to Airtalk Wireless, these commands clear stale entries from the local DNS cache and force immediate resolution of subsequent queries. Running scutil --dns displays the current DNS configuration, helping you verify that changes took effect.

Network settings

To change DNS servers on Mac, open System Settings > Network, select your active connection (Wi-Fi or Ethernet), click Details, and navigate to the DNS tab. Add servers such as 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) by clicking the + button. Some users reported success by switching to Level3 DNS servers (4.2.2.2 or 4.2.2.1) when other options failed. For persistent issues, Apple Communities discussions note that disabling IPv6 under Network > TCP/IP can resolve slow wireless DNS lookups in certain environments.

The implication: Mac DNS changes are device-scoped by default—router-level changes reach every connected device simultaneously.

Is 1.1.1.1 still fastest DNS?

Cloudflare’s 1.1.1.1 resolver remains competitive in 2026, though the DNS landscape has evolved with broader adoption of DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT). DNSPerf benchmarks continue to show strong global performance, but “fastest” depends heavily on your geographic location and the specific routes your traffic takes to reach Cloudflare’s anycast infrastructure. The answer isn’t universal—benchmarking your actual connection matters more than relying on published rankings.

1.1.1.1 vs 8.8.8.8

Both Cloudflare and Google operate globally distributed anycast networks designed to route users to the nearest point of presence. DNSPerf, which provides analytics from millions of real-user tests, shows that performance rankings fluctuate based on network congestion and routing changes. For most users in North America and Europe, the difference between 1.1.1.1 and 8.8.8.8 falls within margin of error. Some gaming-focused communities debate whether one resolver reduces latency for competitive play, but independent benchmarks rarely show meaningful advantages for typical browsing scenarios.

Gaming performance

Gaming communities frequently ask whether DNS choice affects competitive latency, but DNS resolution only occurs when your game connects to a new server or service—once an IP is cached, DNS is irrelevant until that cache expires or you connect elsewhere. Forum discussions on Tom’s Hardware suggest that other factors like geographic server location, network jitter, and bandwidth matter far more than which public DNS resolver you use. Running a continuous ping test to your game’s server while using different resolvers provides more actionable data than generic speed comparisons.

How to benchmark DNS performance

Several tools help you identify the fastest DNS resolver for your specific location and network conditions. Namebench, which analyzes TCP dump, browser history, and datasets to recommend optimal DNS settings, takes approximately 5–10 minutes to complete a thorough test across Windows, Mac, and UNIX according to Download3K documentation. The Gibson Research DNS Benchmark compares cached, uncached, and dotcom lookups using bar charts and tables, testing approximately 70 servers by default with an option to add custom lists of 4,000 or more for more comprehensive analysis.

• Namebench: Uses your browser history and TCP dump for personalized recommendations (5–10 min)
• GRC DNS Benchmark: Advanced charts show cached vs uncached performance (Windows/Linux)
• DNSPerf: Real-world data from millions of tests across 200+ global locations
• DNS Speed Test: Browser-based tool benchmarking 28+ DoH servers without installation

The implication: benchmark tools reveal that the “fastest” DNS for your neighbor may differ from yours—personalized testing beats generic recommendations.

Fix slow DNS at the router level

When DNS problems affect every device on your network, changing settings at the router level fixes all of them simultaneously. Router DNS changes vary significantly by model, but the general principle involves accessing your router’s administrative interface and updating the DNS server addresses under WAN or LAN settings. According to Download3K documentation, most routers accept standard IP addresses like 1.1.1.1 and 8.8.8.8 without special configuration. The benefit: any device that connects to your network—whether it’s a laptop, phone, smart TV, or IoT gadget—inherits the faster DNS without individual configuration.

The implication: router-level DNS changes reach every device on your network, but firmware quirks can silently revert your settings—document what you changed.

Confirmed facts and uncertainties

Community reports consistently confirm that clearing DNS caches resolves most slow lookup complaints. Both Cloudflare (1.1.1.1) and Google (8.8.8.8) address slow loads frequently, and switching away from ISP-provided DNS servers typically provides measurable improvement. However, some aspects remain less certain: whether 1.1.1.1 faces specific restrictions in certain markets, the precise millisecond reduction achievable with different fixes, and which resolver performs best for users in less-studied regions.

What’s confirmed

• Flushing DNS cache clears stale entries and forces fresh lookups
• Public DNS servers like 1.1.1.1 and 8.8.8.8 outperform many ISP defaults
• Benchmark tools like Namebench and GRC DNS Benchmark provide personalized recommendations
• Router-level DNS changes affect all network devices simultaneously

What’s unclear

• Specific reasons why 1.1.1.1 may be restricted in some markets
• Quantified speed improvements (in milliseconds) for each specific fix
• Optimal DNS resolver by region for European versus North American users

“By finding and connecting to the best DNS server in your region you can literally double web browsing speeds in some cases.” — Download3K (Tech Writer)

“It hunts down the fastest DNS servers available for your computer to use.” — Microsoft Q&A (Tech Support)

“Oh WOW! that made a huge difference here (wireless coffee shop in Las Vegas) it’s almost instant now – great suggestion thank you” — Apple Communities (User)

Related reading: How to Hard Reset iPhone · Spectrum Internet Customers Loss

This guide covers Windows, Mac and routers, while the Windows and Android fixes guide delivers essential Android tweaks alongside similar Windows steps for quicker resolution.

Frequently asked questions

Bottom line: Slow DNS lookups are a solvable internet performance problem for most users. The typical fix involves flushing your DNS cache, switching to a public resolver like 1.1.1.1 or 8.8.8.8, and optionally running a benchmark tool like Namebench to confirm you’re using the fastest option for your location. Users report noticeably faster page loads after applying these changes. Run the appropriate flush command for your OS, pick a reputable public DNS, and test over 48 hours before assuming the problem is solved.