How to Fix Slow DNS Lookups on Windows

If you want to know how to fix slow DNS lookup problems on Windows, start by flushing the DNS cache with ipconfig /flushdns, then test your DNS server with nslookup and switch to a faster, reliable resolver if it responds slowly. Most delays come from an unreachable first DNS server, a stale cache, or VPN and security software intercepting queries, and each has a quick test.

What Causes Slow DNS Lookups on Windows?

Slow DNS lookups happen when Windows waits too long for an answer to "what IP address belongs to this name?" before it can open a website or connect to a server. DNS (the Domain Name System) is the internet's address book, and every new site, app update or file share starts with a lookup.

The usual causes are:

• An unresponsive preferred DNS server. Windows asks the first server in its list and only moves to the next one after waiting. If the first server is down or overloaded, every new name costs you that waiting time.
• A slow router or ISP resolver. Many home routers forward DNS to the ISP, and either can be the bottleneck.
• Stale or negative cache entries. Windows keeps recent answers, including "name does not exist" answers. A cached failure can make a working site look broken.
• VPN, proxy or security software that routes DNS through its own filter or a distant server.
• Wrong DNS settings on a work network, such as a public resolver configured on a PC that needs the company's internal DNS to find domain resources.

How Do You Tell If DNS Is Really the Problem?

DNS is the culprit when sites take a second or two to start loading but download quickly once they begin, and when pinging an IP address is fast but pinging a name is slow. Run these checks in order:

1. Open Start, type cmd, right-click Command Prompt and choose Run as administrator.
2. Run ipconfig /all and note the DNS Servers listed for your active adapter.
3. Ping the first DNS server by IP, for example ping 192.168.1.1. No reply or high times suggests a network problem between you and that server (some servers block ping, so treat this as a hint).
4. Run nslookup example.com. If the answer takes several seconds or shows a timeout before succeeding, the resolver is slow.
5. In PowerShell, run Measure-Command { Resolve-DnsName example.com -DnsOnly } to time a lookup in milliseconds. Repeat it with -Server 1.1.1.1 or another resolver to compare.

Note that nslookup bypasses the Windows DNS cache and asks your configured server directly, which is exactly what you want when testing the server itself. Microsoft's DNS client troubleshooting guide uses the same sequence.

How Do You Flush the DNS Cache in Windows?

Run ipconfig /flushdns in an elevated Command Prompt; Windows confirms with "Successfully flushed the DNS Resolver Cache." This clears every stored answer, so the next lookup for each name goes to the DNS server fresh.

1. Open Command Prompt as administrator.
2. Optionally run ipconfig /displaydns to see what is cached. An entry showing "Name does not exist" for a site that should work is a cached failure.
3. Run ipconfig /flushdns.
4. In PowerShell, Clear-DnsClientCache does the same job.

Flushing fixes problems caused by old answers, for example after a website moved servers or you changed DNS settings. It does not make a slow server faster, so if lookups are still slow afterwards, move on to changing the server.

How Do You Change DNS Servers in Windows 11?

Change DNS servers in Settings → Network & internet, select your Wi-Fi or Ethernet connection, then edit the DNS server assignment and enter new addresses manually. Pick a resolver with a good reputation for speed and reliability, or your ISP's resolver if it tests faster.

1. Open Settings → Network & internet.
2. For Wi-Fi, choose Wi-Fi → Manage known networks and select your network (or select the connection's properties). For a cable, choose Ethernet.
3. Next to DNS server assignment, select Edit.
4. Change Automatic (DHCP) to Manual and turn on IPv4.
5. Enter a Preferred DNS and an Alternate DNS address from your chosen provider.
6. Optionally set DNS over HTTPS to On (automatic template) if the provider supports it. Leave Fallback to plaintext on if you want lookups to continue when encryption fails.
7. Select Save, then flush the cache and test again with nslookup.

DNS over HTTPS (DoH) encrypts lookups so others on the network cannot read them. According to Microsoft's network settings help page, this option is in Windows 11 but not Windows 10. If your PC still runs Windows 10, see our explainer on what Windows 10 end of life means, because unsupported systems also stop receiving networking fixes.

What If Changing DNS Doesn't Help?

If lookups stay slow with a fast resolver, the delay is usually in the network path or in software on the PC rather than DNS itself. Work through these in order, testing after each:

1. Disconnect the VPN and pause any web-filtering or security add-on, then test again. If speed returns, adjust that product's DNS or split-tunnel settings.
2. Check the hosts file at C:\Windows\System32\drivers\etc\hosts. Unexpected entries can redirect names; remove anything you did not add.
3. Disable unused adapters (old VPN or virtual adapters) in Settings → Network & internet → Advanced network settings, because Windows may try their DNS servers too.
4. Reset the network stack in an elevated Command Prompt with netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew and ipconfig /flushdns, then restart.
5. As a last resort, use Settings → Network & internet → Advanced network settings → Network reset. It removes and reinstalls network adapters, so note any Wi-Fi passwords and VPN settings first.

Antivirus that inspects web traffic can add noticeable delay to every lookup. If you are reviewing your protection, our roundup of the best antivirus for Windows 11 compares lighter options.

How Is DNS Different on a Business or Domain Network?

On a domain network, PCs must use the company's internal DNS servers, usually the domain controllers, rather than a public resolver. Active Directory publishes the locations of domain controllers and services in DNS, so a PC pointed at a public resolver may browse the web quickly but fail to find file shares, apply Group Policy or sign in to the domain.

For slow lookups at work, check that the internal DNS servers forward external queries to a responsive upstream resolver, and that clients list only internal servers. If you run a small office server, our guide to FSMO roles in Active Directory explains the other single points of failure worth monitoring.

A Common Mistake We See

A frequent pattern is a PC with a manually set DNS server that was right for an old router, ISP or office and was never changed back. Everything works, just slowly, because Windows waits on a server that no longer answers before trying the alternate.

After moving house, changing ISP or swapping a router, run ipconfig /all and confirm the DNS servers make sense. When in doubt, set the assignment back to Automatic (DHCP), test, and only then choose a manual resolver. This one check fixes many "slow internet" complaints on otherwise healthy Windows 11 PCs.

Frequently Asked Questions

Does ipconfig /flushdns speed up the internet?

Not directly. Flushing removes stored DNS answers, which fixes failures and wrong addresses caused by stale entries. It can make the next few lookups slightly slower while the cache refills. If browsing is slow because your DNS server responds slowly, changing to a faster resolver is the real fix.

How do I know which DNS server is fastest for me?

Time lookups against each candidate from your own connection. In PowerShell, run Measure-Command { Resolve-DnsName example.com -DnsOnly -Server <address> } several times per server, using different site names, and compare the averages. Speed depends on your location and ISP, so results differ between homes and offices.

Why is DNS slow only on Wi-Fi?

Wi-Fi and Ethernet are separate adapters with their own DNS settings, so one may point to a slow or old server. Weak signal also adds packet loss, and lost DNS packets wait for a timeout before retrying. Check the Wi-Fi adapter's DNS server assignment and test near the router.

Can a VPN cause slow DNS lookups?

Yes. Many VPNs send all DNS queries through their own servers, which may be far away or busy. Some also keep their adapter's DNS active after disconnecting. Test with the VPN off; if lookups speed up, use a nearer VPN location or the app's split-tunnel and DNS options.

Is DNS over HTTPS slower?

Encrypted DNS adds a little setup work for the secure connection, but the connection is reused, so everyday lookups are usually not noticeably slower. If a DoH template is wrong or blocked, lookups can stall, which is what the Fallback to plaintext setting helps with in Windows 11.

How do I fix slow DNS lookups on Windows 10?

The same steps apply: ipconfig /flushdns, test with nslookup, then change DNS servers in the adapter's IPv4 properties. Windows 10 lacks the built-in DNS over HTTPS setting in Settings, and as it no longer receives free security updates, upgrading is worth considering.

Conclusion

Knowing how to fix slow DNS lookup delays comes down to three moves: clear the cache, measure your resolver, and switch to a faster one or remove whatever is intercepting queries. If an outdated PC is part of the problem, a genuine Windows 11 Pro product key gives you current networking features, including DNS over HTTPS in Settings.

Useful Links