DNS Server Not Responding: Causes and Fixes

What Does the "DNS Server Not Responding" Error Mean

The "DNS server not responding" error occurs when your device cannot get a response from a DNS server while trying to convert a domain name (e.g., google.com) into an IP address. As a result, the browser shows messages like DNS_probe_finished_nxdomain or "The server's IP address could not be found," and the internet seems unavailable, even though the physical network connection may be stable.

Symptoms:

• Websites don't load, but pings to IP addresses work (e.g., ping 8.8.8.8).
• The error appears in the browser (Chrome, Firefox) or system notifications.
• Windows network diagnostics (Network and Sharing Center) indicate a DNS problem.

Common Causes

1. Issues with your ISP or DNS server — a temporary outage on the provider's side or the selected DNS (e.g., 192.168.1.1 from your router).
2. Incorrect DNS settings in your system — a manually configured non-existent or unreachable DNS server.
3. Firewall or antivirus blocking DNS queries — especially aggressive security settings.
4. Corrupted DNS cache — the cache contains outdated or incorrect records.
5. Outdated or conflicting network adapter drivers — especially after an OS update.
6. Software conflicts — VPN, network optimization, or parental control programs may intercept DNS.

Solutions

Method 1: Check Connection and Restart Network Hardware

Sometimes the issue is due to a temporary router or modem glitch. A simple restart often fixes it.

1. Restart your router/modem: unplug it for 30 seconds, then plug it back in. Wait for it to fully boot (blinking lights should become steady).
2. Reconnect to Wi-Fi or try a different router port for your Ethernet cable.
3. Test internet on another device (phone, tablet). If the error appears there too, the problem is with your ISP—contact their support.

💡 Tip: If other devices have internet but yours doesn't, the issue is definitely on your computer—proceed to the next methods.

Method 2: Switch to Public DNS Servers

Using public DNS from Google or Cloudflare often resolves the issue, as these servers are reliable and responsive.

For Windows 10/11:

1. Open Control Panel → Network and Internet → Network and Sharing Center.
2. Click Change adapter settings.
3. Right-click your active connection (e.g., Ethernet or Wi-Fi) and select Properties.
4. Select Internet Protocol Version 4 (TCP/IPv4) → Properties.
5. Check Use the following DNS server addresses and enter:
   • Preferred DNS server: 8.8.8.8
   • Alternate DNS server: 8.8.4.4 (or Cloudflare: 1.1.1.1 and 1.0.0.1)
6. Click OK and close the windows.

Or via PowerShell (as Administrator):

# Replace "Ethernet" with your connection name (find it with: Get-NetAdapter)
netsh interface ip set dns "Ethernet" static 8.8.8.8
netsh interface ip add dns "Ethernet" 8.8.4.4 index=2

For Linux (Ubuntu/Debian with NetworkManager):

# Specify your connection name (list with: nmcli con show)
nmcli con mod "Wired connection 1" ipv4.dns "8.8.8.8 1.1.1.1"
nmcli con mod "Wired connection 1" ipv4.ignore-auto-dns yes
nmcli con up "Wired connection 1"

For static settings in /etc/resolv.conf (not recommended, as the file may be overwritten):

echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf

For macOS (Sonoma and newer):

1. System Settings → Network.
2. Select your active interface (Wi-Fi or Ethernet) → Details → DNS.
3. Click + and add 8.8.8.8, then 8.8.4.4.
4. Remove any old DNS servers if present.
5. Click OK → Apply.

Or via Terminal:

# For Wi-Fi (replace "Wi-Fi" with your interface name if different)
sudo networksetup -setdnsservers Wi-Fi 8.8.8.8 1.1.1.1
# Verify settings:
networksetup -getdnsservers Wi-Fi

Method 3: Flush the DNS Cache

A corrupted or outdated DNS cache can cause the error. Clear it for your OS.

Windows:

Open Command Prompt or PowerShell as Administrator:

ipconfig /flushdns

Output: Successfully flushed the DNS Resolver Cache.

Linux (systemd-resolved):

sudo systemd-resolve --flush-caches
# Or restart the service:
sudo systemctl restart systemd-resolved

For nscd:

sudo /etc/init.d/nscd restart

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

For macOS versions before 10.10:

sudo discoveryutil mdnsflushcache

Method 4: Temporarily Disable Firewall and Antivirus

Some security software (e.g., Kaspersky, Avast, Windows Defender Firewall) may block DNS queries.

1. Windows Defender Firewall:
   • Open Control Panel → Windows Defender Firewall → Turn Windows Defender Firewall on or off.
   • Turn it off for both private and public networks (diagnosis only!).
2. Antivirus: locate the Web Protection or Network Shield component in settings and disable it for 5–10 minutes.
3. Check if the error disappears. If yes, configure an exception for DNS queries (port 53) in your antivirus.

⚠️ Important: Do not leave your firewall/antivirus disabled for long. Re-enable them immediately after testing.

Method 5: Update Network Adapter Drivers

Outdated drivers can disrupt DNS client functionality.

Windows:

1. Press Win + X → Device Manager.
2. Expand Network adapters.
3. Right-click your adapter (e.g., Realtek PCIe GBE Family Controller) → Update driver.
4. Choose Search automatically for updated driver software.
5. Restart your computer.

Linux:

# For repository drivers (Ubuntu/Debian):
sudo apt update && sudo apt upgrade
# Or reinstall the driver (example for r8169):
sudo apt install --reinstall r8168-dkms

macOS:

Driver updates are included in system updates. Go to System Settings → Software Update and install all updates.

Method 6: Reset Network Settings (Last Resort)

If nothing else works, perform a full network settings reset. This will remove all Wi-Fi, VPN, and adapter configurations.

Windows 10/11:

1. Windows Settings → Network & Internet → Advanced network settings.
2. Click Network reset → Reset now.
3. Confirm and restart your computer. After resetting, you'll need to reconnect to Wi-Fi.

macOS:

# Delete network configurations (back up Wi-Fi passwords first!)
sudo rm /Library/Preferences/SystemConfiguration/com.apple.network.eppc.plist
sudo rm /Library/Preferences/SystemConfiguration/com.apple.vmnet.plist
# Reboot:
sudo reboot

Reconfigure your network after restart.

Linux (Ubuntu):

sudo rm /etc/resolv.conf
sudo reboot

(The resolv.conf file will regenerate automatically if systemd-resolved or NetworkManager is used.)

Prevention

To avoid recurring "DNS server not responding" errors, follow these simple rules:

1. Use reliable public DNS — Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare (1.1.1.1). They're more stable than ISP-provided DNS.
2. Keep your OS and drivers updated — especially network adapters. Enable automatic updates.
3. Avoid installing dubious software — some "internet booster" utilities can mess with DNS settings.
4. Check physical connections — a faulty cable or weak Wi-Fi signal can sometimes cause disruptions.
5. Flush DNS cache monthly — especially after changing DNS or installing updates.
6. Configure a backup DNS — in your network settings, specify two DNS servers (primary and secondary) so if one fails, the other works.

If the problem occurs frequently, contact your internet provider—their DNS servers may be unstable.