How to Fix DNS Server Not Responding — Step-by-Step Guide
“DNS Server Not Responding” prevents all websites from loading even when your internet connection is working. DNS translates domain names to IP addresses — without it, browsers can’t find any website. Test your connection at instantspeedtest.net/ — if even this fails to load, follow this guide.
DNS Not Responding Fixes — Fastest to Most Complex
| Fix | How To | Fixes |
|---|---|---|
| Flush DNS cache | Admin CMD: ipconfig /flushdns |
Stale cache entries |
| Change DNS servers | Network adapter → Properties → IPv4 → 1.1.1.1 / 8.8.8.8 | ISP DNS outage |
| Restart router/modem | Power cycle 30 seconds | Router DNS cache corruption |
| Release and renew IP | Admin CMD: ipconfig /release then ipconfig /renew |
DHCP assignment issue |
| Reset TCP/IP stack | Admin CMD: netsh int ip reset |
Corrupted network config |
| Disable IPv6 temporarily | Network adapter → Properties → uncheck IPv6 | IPv6 DNS resolution conflicts |
| Check Windows Firewall | Allow DNS (port 53 UDP/TCP) through firewall | Firewall blocking DNS |
The Fastest Fix — Changing DNS Takes 60 Seconds
The single fastest DNS fix: open Network Connections (Win+R → ncpa.cpl) → right-click your active adapter → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → Use the following DNS server addresses → Preferred: 1.1.1.1, Alternate: 1.0.0.1. Click OK. Open a new browser tab and test a website. Cloudflare’s 1.1.1.1 averages 11ms response globally vs ISP DNS averaging 40–80ms — faster AND more reliable. This single change fixes ISP DNS outages and improves daily browsing speed. See our full DNS guide.
Related Guides
- Best DNS Servers for Speed
- What Is DNS?
- Internet Fast But Pages Slow
- WiFi Connected No Internet
- Fix Slow Internet Windows 11
- What Is a DNS Leak?
Frequently Asked Questions
What causes “DNS server not responding” on Windows?
Most common causes in order: ISP’s DNS server is temporarily down or overloaded; stale or corrupted DNS cache on your computer or router; Windows DNS Client service stopped (rare); network adapter driver issue; third-party security software intercepting DNS queries. The change-DNS fix (above) resolves ISP DNS issues instantly. The flush-cache fix resolves stale entries. If neither works, netsh winsock reset in admin CMD followed by a restart resolves most remaining cases.
Will changing DNS affect my internet speed?
Positively — switching from ISP DNS (40–80ms average) to Cloudflare 1.1.1.1 (11ms average) or Google 8.8.8.8 (20ms average) reduces the time each new website takes to resolve its domain. This makes pages feel noticeably faster to start loading, though it doesn’t change your download bandwidth. The improvement is most noticeable on pages that load resources from many different domains (news sites, e-commerce sites) where multiple DNS lookups occur per page load.