The fastest fix for slow DNS lookup is switching to a faster public DNS resolver, like Cloudflare (1.1.1.1) or Google (8.8.8.8), which takes under five minutes and solves the problem for most people immediately. If that alone doesn’t fix it, flushing your DNS cache and checking your router’s firmware are the next two things to try.
DNS lookup is the step that happens before a page even starts loading: your device has to translate a web address into an actual server location, and if that step is slow, everything else feels slow too, even on a fast connection. It’s also one of the most overlooked causes of a browser that feels sluggish for no obvious reason.
Switch to a faster DNS resolver
Your internet provider’s default DNS server is often slower than dedicated public alternatives. Switching is usually the single highest-impact fix:
- Cloudflare: 1.1.1.1 and 1.0.0.1, generally the fastest public option and privacy-focused.
- Google: 8.8.8.8 and 8.8.4.4, reliable and widely used.
- Quad9: 9.9.9.9, a strong third option that also blocks known malicious domains by default.
You can set these at the router level (applies to every device on your network) or on an individual device, under network settings, in the DNS configuration field.
Flush your DNS cache
A stale or corrupted local DNS cache can serve slow or outright wrong records for sites you’ve visited before. The command differs by operating system:
- Windows: open Command Prompt and run
ipconfig /flushdns. - macOS: open Terminal and run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. - Linux: the command depends on your setup, but
resolvectl flush-cachesworks on systemd-based systems, or restart your local resolver service (likesudo systemctl restart dnsmasqif you’re running dnsmasq).
Enable DNS prefetching in your browser
In Chrome, go to chrome://settings/performance and make sure Preload pages is enabled. This resolves DNS for links on the current page in the background, before you actually click them, which makes navigation feel faster even though the underlying lookup speed hasn’t changed.
Turn on DNS over HTTPS (DoH)
DNS over HTTPS encrypts your DNS queries and often routes them through faster infrastructure than standard unencrypted DNS. In Chrome, go to chrome://settings/security and enable Use secure DNS.
Update your router’s firmware
Outdated router firmware can carry DNS relay bugs that quietly add 50 to 200 milliseconds to every single lookup, an amount that’s individually small but adds up across a normal browsing session. Log into your router’s admin panel and check for available firmware updates.
Rule out your VPN or antivirus software
VPNs and some antivirus/security suites route DNS queries through their own servers or inspect them before passing them along, both of which add latency. If slow lookups started right after installing a VPN or security tool, temporarily disable it and re-test before assuming the problem is your DNS resolver or router.
Restart your router and modem
A simple restart clears a router’s internal DNS cache and any accumulated network state that can quietly degrade performance over weeks of uptime, the same logic that applies to restarting a slow computer. Unplug both the router and modem, wait about 30 seconds, then power the modem back on first, followed by the router once it’s reconnected.
How to know if DNS is actually your problem
A DNS lookup time under 50ms is considered normal; anything consistently above 200ms is worth addressing. You can check this in most browsers’ developer tools under the Network tab, looking at the DNS timing for a given request. For a more direct measurement outside the browser, the dig command (macOS/Linux) or nslookup (all platforms) will show you the exact resolution time for a specific domain from the command line, which is useful for comparing resolvers directly rather than relying on how a page “feels.”
Frequently asked questions
Will changing my DNS server affect my privacy?
It changes who sees your DNS queries. Your ISP’s default DNS can see and potentially log every site you look up; switching to Cloudflare or Google’s DNS shifts that visibility to them instead, both of which publish privacy-focused policies for their public DNS services specifically.
Do I need to change DNS settings on every device, or just my router?
Changing it at the router level applies to every device on your network automatically, which is more convenient than configuring each device individually. Individual device settings are useful if you want different DNS servers for different devices, like a work laptop versus a home computer.
Can slow DNS affect video calls or gaming, not just web browsing?
DNS lookup happens at the start of a connection, so it mainly affects how quickly a service is initially reached, not the ongoing quality of a call or game session once connected. That said, ongoing lag in either case is more likely a general network or bandwidth issue than a DNS problem specifically.
Is DNS over HTTPS always faster than regular DNS?
Not universally, but it’s frequently faster in practice because DoH providers often run on infrastructure optimized for speed, and it adds a security benefit (encryption) that plain DNS doesn’t have, regardless of the speed difference.