What you will achieve
Faster hostname resolution on Windows by identifying slow DNS servers and switching to reliable resolvers.
1) Measure the symptom
Slow DNS feels like a long pause before a site starts loading, while the page itself loads quickly once started. Test with:
nslookup www.microsoft.com
nslookup www.microsoft.com 1.1.1.1
If the second command returns much faster, your configured DNS server is likely the bottleneck.
2) See which DNS Windows is using
ipconfig /all
Check DNS Servers under your active adapter. Router-provided DNS (192.168.x.1) is common but not always fast or trustworthy.
3) Set reliable public resolvers
- Settings → Network & internet → Wi‑Fi or Ethernet → hardware properties.
- Edit DNS → Manual → IPv4 on.
- Enter primary and secondary servers, e.g. Cloudflare
1.1.1.1and1.0.0.1, or Google8.8.8.8and8.8.4.4, or Quad99.9.9.9. - Save, then flush DNS.
4) Disable DNS over HTTPS for testing
Settings → Privacy & security → DNS over HTTPS — set to Off temporarily to see if DoH provider conflicts with manual DNS. Re-enable with a provider you trust once stable.
5) Router and VPN interactions
- VPN clients often force their own DNS — disconnect VPN while testing.
- Router DNS proxy or parental controls can add latency — test with manual DNS on the PC.
Verify
Browse several sites you use daily. Run nslookup again — response times should be consistently low (often under 50 ms to a good resolver).