Skip to content
FixingBook
Verifiedbeginnerest. 10 minutes

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.

dnsbrowser-erroripconfig

Confirmed working on: Windows 10 · Windows 11

Before you begin

Match the environmentUse this guide only for Windows 10, Windows 11 or a clearly compatible setup.
Protect recoveryBack up important data and save encryption or account recovery keys before changing system state.
Know when to stopMake one change at a time and stop if the result differs from what the guide describes.

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

  1. Press Windows Key + R, type ncpa.cpl, and hit Enter.
  2. Right-click your active network connection (Wi-Fi or Ethernet) and choose Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Select Use the following DNS server addresses.
  5. Enter 8.8.8.8 for the Preferred DNS server.
  6. Enter 8.8.4.4 for the Alternate DNS server.
  7. Click OK to save and apply the settings.
Expert Tip

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

  1. Open the Start Menu, type cmd, right-click Command Prompt, and select Run as administrator.
  2. Type the following command and press Enter:
    ipconfig /flushdns
  3. Type this command to reset the TCP/IP stack:
    netsh int ip reset
  4. Restart your computer for the changes to take effect.

Solution 3: Reset the Winsock catalog

  1. Open Command Prompt as administrator.
  2. Run the following command:
    netsh winsock reset
  3. Once the command completes, restart your PC immediately.
  4. Try browsing the web again to see if the DNS error is resolved.

Solution 4: Restart the DNS Client service

  1. Press Windows Key + R, type services.msc, and press Enter.
  2. Scroll down and locate the DNS Client service.
  3. Right-click it and select Restart.
  4. If the option is grayed out, open Command Prompt as admin and run:
    net stop dnscache
    net start dnscache
Caution

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

  1. Repeat the exact action that originally triggered the problem.
  2. Confirm the original error or symptom is gone and no new warning has appeared.
  3. If the guide changed a driver, service, package, or system setting, restart once and test again.
  4. 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

Consensus0%
Required100% (Weight 3)
Contributors0
Verified By YouNo
Your Weight--

Did this solution resolve your issue?

Confirming if this works strengthens verification statistics on the registry.

Sign In to VerifySign in required to verify

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.

Spotted something outdated? Suggest an edit. Maintainers review submissions within 48 hours.
Share:XReddit

Discussion (0)

No comments yet. Share your experience or verify if this fixed your issue!

Join the Discussion