Fix DNS Server Not Responding Error
The operating system fails to translate domain names to IP addresses due to an unresponsive DNS server, preventing web browsing.
Confirmed working on: Windows 10 · Windows 11
Before you begin
Problem overview
Your web browser fails to load pages and displays a “DNS Server Not Responding” or “ERR_NAME_NOT_RESOLVED” error. This means your computer cannot translate readable domain names into IP addresses.
Common causes
- Unreliable or overloaded ISP DNS servers
- A corrupted local DNS cache
- Network adapter driver bugs
- Third-party antivirus or firewall intercepting DNS traffic
Solution 1: Change to a public DNS provider
- Press
Windows Key + R, typencpa.cpl, and hit Enter. - Right-click your active network connection (Wi-Fi or Ethernet) and choose Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Select Use the following DNS server addresses.
- Enter
8.8.8.8for the Preferred DNS server. - Enter
8.8.4.4for the Alternate DNS server. - Click OK to save and apply the settings.
You can also use Cloudflare’s DNS by entering 1.1.1.1 and 1.0.0.1. This is often faster than standard ISP servers.
Solution 2: Flush the DNS cache
- Open the Start Menu, type
cmd, right-click Command Prompt, and select Run as administrator. - Type the following command and press Enter:
ipconfig /flushdns - Type this command to reset the TCP/IP stack:
netsh int ip reset - Restart your computer for the changes to take effect.
Solution 3: Reset the Winsock catalog
- Open Command Prompt as administrator.
- Run the following command:
netsh winsock reset - Once the command completes, restart your PC immediately.
- Try browsing the web again to see if the DNS error is resolved.
Solution 4: Restart the DNS Client service
- Press
Windows Key + R, typeservices.msc, and press Enter. - Scroll down and locate the DNS Client service.
- Right-click it and select Restart.
- If the option is grayed out, open Command Prompt as admin and run:
net stop dnscache net start dnscache
If you use a third-party antivirus like Avast or Bitdefender, try temporarily disabling their “Web Shield” or “Network Protection” features. These modules can sometimes falsely block legitimate DNS requests.
Confirm the result
- Repeat the exact action that originally triggered the problem.
- Confirm the original error or symptom is gone and no new warning has appeared.
- If the guide changed a driver, service, package, or system setting, restart once and test again.
- If the result is worse or unexpected, stop. Reverse only the last change using its documented restore option; if none is documented, use your backup or qualified support.
Questions about this fix
What does DNS Server Not Responding mean?
It means your computer cannot reach the server responsible for translating web addresses (like google.com) into IP addresses.
Can a third-party antivirus cause DNS issues?
Yes, strict firewall or web shield settings in antivirus programs can sometimes block outgoing DNS requests.
Did this fix work for you?
Weighted Consensus Protocol
Did this solution resolve your issue?
Confirming if this works strengthens verification statistics on the registry.
FixingTeam10,000 rep
Official Project Maintainers
The core engineering and moderation team behind FixingBook. We curate, verify, and maintain the standards of the troubleshooting ledger.
Related fixes
Fix Wi-Fi Connected But No Internet Access
Devices successfully authenticate and connect to the local Wi-Fi router but cannot reach external websites. This typically points to DNS failures, router WAN issues, or ISP outages.
Discussion (0)
No comments yet. Share your experience or verify if this fixed your issue!
