How to Fix DNS Server Not Responding: The Complete 2026 Guide

It’s a scenario that can bring your work to a frustrating halt: you’re connected to the internet, but no websites will load. Instead, your browser displays the dreaded “DNS server not responding” error. This issue is more common than you might think, but the good news is that it’s almost always fixable, often in just a few minutes.

This comprehensive guide will walk you through exactly what this error means and provide a step-by-step troubleshooting process to get you back online. We’ll cover solutions for Windows, Mac, and other devices, starting with the quickest and easiest fixes and moving to more advanced solutions if needed.

What Does “DNS Server Not Responding” Mean?

Before diving into the fixes, it helps to understand the underlying problem. The Domain Name System (DNS) acts as the internet’s phonebook . When you type a human-friendly website name like “google.com“ into your browser, your device contacts a DNS server to find the corresponding, machine-readable IP address (like 142.250.190.46). Your browser needs this IP address to load the website.

The “DNS server not responding” error means your device sent a request to the DNS server but did not receive a reply . This prevents the domain name from being translated, so your browser has no way to find the website you’re trying to reach. Your internet connection might be working perfectly, but without a functioning DNS server, you can’t access any websites by their names .

How to Confirm DNS is the Problem

Before you start troubleshooting, it’s useful to confirm that DNS is the root of the issue. A simple test can help you differentiate a DNS problem from a broader internet connectivity failure.

Ping a Website: Try pinging a website by its domain name. Open your command prompt (Windows) or terminal (macOS) and type ping google.com. If you get a “Ping request could not find host” or similar error, it’s likely a DNS issue.
Ping an IP Address: Next, ping a known IP address directly. In the same command line, type ping 8.8.8.8. This IP address belongs to Google’s public DNS server.
- If the ping to 8.8.8.8 succeeds but the ping to google.com fails, it confirms your internet connection is working, but DNS resolution is failing .
- If the ping to 8.8.8.8 fails, your device is not connected to the internet, and the problem is with your network connection, not specifically DNS.

How to Fix “DNS Server Not Responding”: Step-by-Step

Follow these troubleshooting steps in order. They are arranged from the simplest and fastest solutions to the more involved ones. The process below covers methods from multiple expert sources .

Step 1: Quick & Simple Checks

These are the first things to try, as they resolve a large percentage of DNS errors.

Restart Your Router and Device: A power cycle can clear temporary glitches in your router’s memory and refresh its connection to your Internet Service Provider (ISP) .
- How to do it: Unplug your router’s power cable, wait at least 30 seconds, and plug it back in. Allow it to fully restart (this can take a minute or two). Also, restart the computer or device you were using.
Try a Different Web Browser: Open a different browser (e.g., switch from Chrome to Firefox or Edge) and try to load the same website. If it works, the issue is likely with your original browser’s cache or settings, not your network .
Test on a Different Device: Check if the problem is isolated to one device by attempting to load a website on another device connected to the same network (like a smartphone or tablet). If the other device works, the problem is with the original device’s settings .

Step 2: Flush Your DNS Cache

Your computer stores recent DNS lookup results in a local cache to speed up browsing. If this cache becomes corrupted or outdated, it can cause DNS errors . Flushing it forces your device to fetch fresh DNS data.

On Windows:
1. Press the Windows key, type cmd, right-click on “Command Prompt,” and select “Run as administrator.”
2. In the command prompt window, type ipconfig /flushdns and press Enter .
3. A confirmation message, “Successfully flushed the DNS Resolver Cache,” will appear .
On macOS:
1. Open the “Terminal” application (found in Applications > Utilities).
2. Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Enter .
3. Enter your administrator password when prompted. No confirmation message is typically displayed .

Step 3: Change Your DNS Server

Your ISP usually provides a default DNS server, but these can sometimes be slow, unreliable, or experience outages. Switching to a free, public DNS server like Google Public DNS or Cloudflare is a proven and effective fix .

Recommended Public DNS Servers:

Google: 8.8.8.8 (Preferred) and 8.8.4.4 (Alternate)
Cloudflare: 1.1.1.1 (Preferred) and 1.0.0.1 (Alternate)
On Windows:
1. Press Windows + R, type ncpa.cpl, and press Enter to open Network Connections .
2. Right-click your active network connection (Wi-Fi or Ethernet) and select “Properties”.
3. Select “Internet Protocol Version 4 (TCP/IPv4)” and click “Properties” .
4. Select “Use the following DNS server addresses.”
5. Enter a public DNS address in the “Preferred DNS server” field and another in the “Alternate DNS server” field.
6. Click “OK” to save the changes and restart your browser .
On macOS:
1. Go to Apple menu > System Settings > Network .
2. Select your active network connection (e.g., Wi-Fi) and click “Details” .
3. Go to the “DNS” tab.
4. Click the + button to add a new DNS server and enter a public DNS address (e.g., 8.8.8.8) .
5. Repeat to add an alternate DNS server (e.g., 8.8.4.4).
6. Click “OK” and then “Apply” to save the changes .

Step 4: Disable Your Firewall and Antivirus Temporarily

Overly strict firewall or antivirus software can sometimes block DNS traffic, causing the error . Temporarily disable these security programs to see if it resolves the issue.

Important: Only disable your firewall for long enough to test the connection. Re-enable it immediately after testing to keep your system secure . If disabling them resolves the error, you will need to create an exception in the software’s settings to allow DNS traffic (port 53) rather than leaving it disabled .

Step 5: Disable IPv6

While IPv6 is the newer internet protocol, some networks and DNS servers have compatibility issues that cause DNS errors. Temporarily disabling IPv6 can help determine if this is the source of your problem .

On Windows:
1. Open “Network Connections” by pressing Windows + R, typing ncpa.cpl, and pressing Enter.
2. Right-click your active network connection and select “Properties”.
3. Under the “Networking” tab, uncheck “Internet Protocol Version 6 (TCP/IPv6)” .
4. Click “OK” to save the changes and restart your computer .
On macOS:
1. Go to Apple menu > System Settings > Network .
2. Select your active network connection, and click “Details”.
3. Go to the “TCP/IP” tab.
4. Next to “Configure IPv6,” select “Link-local only” from the dropdown menu .
5. Click “OK” to save the changes .

Step 6: Disable Secondary Network Adapters

If your computer has multiple active network connections (e.g., Wi-Fi, Ethernet, and a virtual adapter for a VPN), they can sometimes conflict with each other and cause DNS issues .

Open “Network Connections” by pressing Windows + R, typing ncpa.cpl, and pressing Enter.
Right-click on any secondary or unused connection (like a virtual adapter or an inactive Ethernet port) and select “Disable” .
Restart your browser and try to load the page again.

Step 7: Renew Your IP Address

Renewing your IP address forces your device to ask the router for a new configuration, which can sometimes clear up network-related issues. This step often accompanies flushing the DNS cache .

On Windows (in an administrator Command Prompt):
1. Type ipconfig /release and press Enter. This will release your current IP address.
2. Wait a moment, then type ipconfig /renew and press Enter. This will request a new IP address from the router. This process may take a few moments .

Step 8: Update Your Network Adapter Driver

An outdated or corrupted network adapter driver can lead to communication problems, including DNS errors .

Right-click the Start menu and open “Device Manager.”
Expand the “Network adapters” section.
Right-click your active network adapter (it often has “Wi-Fi” or “Ethernet” in its name) and select “Update driver” .
Choose “Search automatically for drivers.” Windows will look for and install the latest driver .

Step 9: Reset Your Network Settings

If you’ve tried everything else, resetting your network settings to their default state can be a powerful last resort. This will reinstall network adapters and reset related settings to their defaults.

Go to Settings > Network & internet > Advanced network settings.
Under “More settings,” click “Network reset” .
Click the “Reset now” button and confirm.

Step 10: Check for Hardware Issues

If the problem persists on a single computer but other devices on the same network are working, and you’ve tried all the steps above, you may have a hardware issue with your network adapter. Trying a USB-to-Ethernet adapter or a USB Wi-Fi adapter can help you test if your built-in network card is failing .

FAQ

Q1: What is the fastest way to fix the “DNS server not responding” error?

The fastest and most common fix is to restart your router . Unplug it, wait 30 seconds, and plug it back in. If that doesn’t work, flushing your DNS cache is the next best step .

Q2: Will changing my DNS server make my internet faster?

Yes, it can. Sometimes your ISP’s DNS servers can be slow or overloaded. Switching to a public DNS server like Google (8.8.8.8) or Cloudflare (1.1.1.1) often results in faster and more reliable lookups, which can make web browsing feel snappier .

Q3: Why does the “DNS server not responding” error keep coming back?

Recurring DNS issues can be caused by several things:

Outdated router firmware: Check your router’s admin panel for an update .
ISP problems: Your Internet Service Provider might be having a service outage .
Persistent software conflicts: A firewall, antivirus, or VPN might be repeatedly interfering with DNS traffic .
Hardware problems: An old or failing router could be the root cause .

Q4: What do the DNS addresses 8.8.8.8 and 8.8.4.4 do?

These are the IP addresses for Google Public DNS, a free, globally available service that resolves domain names to IP addresses. By manually setting your device to use these addresses, you bypass your ISP’s DNS server, which is often the source of “DNS server not responding” errors .