You click a link, but the page seems to hesitate before anything loads. When that delay occcurs repeatedly across different websites, DNS resolution may be one of the places worth checking.
How to fix slow DNS lookup comes down to finding where that delay occurs and addressing it without changing unrelated network settings along the way.
1. What Causes Slow DNS Lookup?
DNS lookup slows down when your device takes longer than expected to translate a domain name into the IP address needed to reach a website.
Common causes include:
- Slow or overloaded DNS servers
- Stale DNS cache entries
- Router or modem problems
- Network congestion
- Poor performance from an ISP’s default DNS resolver
The delay is not always on your device. A website can also have inefficient DNS or hosting configuration, while pages that depend on many external domains may require additional DNS lookups before all resources can load.
Because several parts of the connection can produce similar symptoms, it is worth testing DNS rather than assuming it is responsible for every slow-loading page.
2. How to Fix Slow DNS Lookup
Start with the least disruptive fixes and test your connection after each one. This makes it easier to identify what actually solved the slowdown instead of changing several network settings at once.
Restart Your Router and Device
Begin with a full restart of both your device and network equipment.
Turn off your computer or phone, unplug the router or modem from power, wait about 30 seconds, then reconnect it. Once the network is available again, restart your device and test several websites.
This can clear temporary router, connection, and resolver issues without changing your network configuration.
Flush the DNS Cache
Your operating system stores recently resolved domain names locally. Clearing this DNS cache forces the device to request fresh DNS information.
- Windows:
Open Command Prompt as Administrator and run: ipconfig /flushdns
Windows should confirm that the DNS Resolver Cache was successfully flushed.
- macOS:
The command depends on the macOS version. On many recent versions, you can open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Because DNS cache commands can change between macOS releases, verify the appropriate command for your current version when necessary.
Change to a Faster Public DNS Server
Your device may be using DNS resolvers supplied automatically by your internet service provider. Switching temporarily to a reputable public resolver can help determine whether those servers are contributing to the delay.
Common options include:
- Cloudflare: 1.1.1.1 and 1.0.0.1
- Google Public DNS: 8.8.8.8 and 8.8.4.4
- Quad9: 9.9.9.9 and 149.112.112.112
There is no single DNS provider that is fastest for every user or location. Test performance from your own network rather than choosing solely from advertised speeds.
Restart the DNS Client Service
If you’re troubleshooting how to fix slow DNS lookup on Windows, the DNS Client service is one area you may want to check because it manages DNS-related functions, including caching resolved names.
In many modern Windows configurations, manually restarting this service may be restricted or unnecessary. Start by flushing the DNS cache and restarting Windows instead.
Advanced users troubleshooting a service-specific problem can inspect DNS Client through the Services console without changing its startup configuration unnecessarily.
Disable VPN or Proxy Temporarily
A VPN or proxy can change the route your DNS requests take or use its own DNS resolver.
Temporarily disconnect the VPN or proxy and repeat the same browsing or DNS test. A noticeable improvement suggests the additional network layer may be contributing to the delay.
Do not leave a VPN disabled when you rely on it for workplace access, privacy, or another specific security requirement. The goal here is simply to isolate the source of the slowdown.
Check Firewall or Antivirus Settings
Security software can inspect or filter network traffic, and incorrect or overly restrictive configurations can occasionally interfere with DNS requests.
When working through how to fix slow DNS lookup, check whether the slowdown began after installing or updating firewall, antivirus, or web-filtering software. Review its DNS, web protection, or network settings rather than permanently disabling security protection.
For a quick diagnostic test, use the software vendor’s recommended temporary troubleshooting procedure and restore protection immediately afterward.
Update Network Drivers
On Windows, outdated or malfunctioning network adapter drivers can cause broader connectivity problems that may appear alongside slow DNS resolution.
Open Device Manager > Network adapters, identify your active adapter, and check for driver updates. For laptops and prebuilt PCs, you can also check the computer manufacturer’s support page for the appropriate driver.
Do not install drivers from unknown third-party download sites.
Restart Your Browser and Clear Browser DNS Cache
One step in understanding how to fix slow DNS lookup is determining whether the problem is limited to your browser. Browsers can maintain their own connection and DNS-related information in addition to the operating system’s cache.
First, fully close and reopen the browser. If the slowdown occurs only in one browser, test the same websites in another browser before making further system-wide changes.
This comparison is useful: if DNS-related delays appear across every browser and application, the cause is more likely to sit at the operating system, router, or DNS resolver level.
>>> Read more: Everything About 5G SIM Card: Who Needs One and How to Get It in 2026
3. How to Test Whether DNS Is the Problem
Before repeatedly changing DNS settings, measure what is actually happening. A few basic tests can help separate DNS resolution delays from general network latency or a slow website.
- Use ping and traceroute
ping checks reachability and network latency, while tracert on Windows or traceroute on macOS/Linux shows the path to a destination. These tools help diagnose network issues but do not directly measure DNS lookup speed.
- Run an NSLookup command
Enter nslookup example.com in Command Prompt or Terminal to see which DNS server responds and what IP address it returns. You can also test another resolver, such as nslookup example.com 1.1.1.1.
- Measure DNS response time
Where available, dig example.com provides a Query time in milliseconds, making it more useful for measuring DNS performance directly.
- Compare different DNS providers
Repeat tests using your current DNS and alternatives such as Cloudflare, Google Public DNS, or Quad9. Test several times because caching and network conditions can affect results.
If DNS responds quickly but websites still load slowly, the problem is probably elsewhere.
4. Best Public DNS Servers to Try
Switching resolvers can be worth testing when how to fix slow DNS lookup points back to poor performance from your current DNS provider. These are four widely used public options:
| Provider | Primary DNS | Secondary DNS | Best For |
| Cloudflare DNS | 1.1.1.1 | 1.0.0.1 | Speed and privacy |
| Google Public DNS | 8.8.8.8 | 8.8.4.4 | Reliability and broad availability |
| Quad9 | 9.9.9.9 | 149.112.112.112 | Blocking known malicious domains |
| OpenDNS | 208.67.222.222 | 208.67.220.220 | Filtering and additional DNS controls |
These addresses come from the providers’ official documentation: Cloudflare 1.1.1.1, Google Public DNS, Quad9, and Cisco OpenDNS.
Do not choose based on reputation alone. DNS performance varies by network and location, so compare response times from your own connection.
5. How to Prevent Slow DNS Lookup in the Future
After working through how to fix slow DNS lookup, a few network-maintenance habits can reduce recurring problems:
- Restart your router when problems appear: A restart can clear temporary network issues, although there is generally no need to reboot a properly functioning router on a fixed schedule.
- Keep your operating system updated: Install current system and network-related updates rather than allowing outdated software to become another troubleshooting variable.
- Use a reliable DNS provider: When your ISP’s resolver consistently performs poorly, consider keeping a reputable public DNS service configured.
- Clear the DNS cache when troubleshooting: Flush cached DNS records when you suspect stale or incorrect resolution rather than doing it routinely without a reason.
- Avoid stacking VPNs and proxies: Multiple network-routing layers can complicate DNS resolution and make performance problems harder to diagnose.
>>> Another helpful blog: Search Google or Type a URL: What’s the Difference?
6. FAQs
How to Speed Up DNS Lookup?
Test your current DNS response time first. If it is consistently slow, try a reputable public DNS resolver, clear stale DNS caches, and check whether a VPN, proxy, or router is contributing to the delay.
How to Fix DNS Lookup Failure?
Check your internet connection, restart the router, flush the DNS cache, and test another DNS resolver. If only one domain fails, the problem may be with that domain’s DNS rather than your network.
Is 1.1.1.1 DNS the Fastest?
Not necessarily. Cloudflare’s 1.1.1.1 is designed as a fast public resolver, but the fastest DNS service for you depends on your location, ISP, routing, and network conditions.
7. Conclusion
A slow website does not automatically mean slow DNS, which is why testing should come before changing network settings. The most effective approach to how to fix slow DNS lookup is to isolate the delay first, then address the responsible cache, resolver, router, or network layer.
When DNS response times are already fast, the bottleneck is likely somewhere else and deserves a different fix.
