The DNS server not responding error appears when your device cannot get a response from the DNS server responsible for resolving website addresses. You may still be connected to Wi-Fi, but websites refuse to load because your computer cannot look up their IP addresses.
The problem can originate from your router, internet service provider (ISP), incorrect DNS settings, or software interfering with network requests.
Fortunately, most DNS connection problems can be diagnosed without advanced technical knowledge. Here are seven practical solutions for Windows and macOS.
What Does DNS Server Not Responding Mean?
The Domain Name System (DNS) translates website names, such as google.com, into IP addresses that computers use to establish connections.
When you enter a website address, your device asks a DNS resolver to find the corresponding IP address.
If the resolver doesn’t respond within the expected time, your browser or operating system may report a DNS error.
Common causes include:
- An unavailable or overloaded DNS resolver.
- Router or internet connection problems.
- Incorrect DNS configuration.
- Outdated locally cached DNS information.
- VPN, proxy, or security software interference.
The important distinction: A DNS server failing to respond is different from a domain name not existing. Identifying which problem you’re experiencing helps you avoid unnecessary fixes.

How to Fix DNS Server Not Responding
Start with the simpler checks before changing network settings.
1. Check Your Internet Connection
First, determine whether the problem affects one website or your entire internet connection.
Try opening several well-known websites. If none load, test the connection on another device.
You can also connect your computer to a different network, such as a mobile hotspot.
These tests provide useful clues:
- All devices affected: The router, ISP, or configured DNS resolver may be responsible.
- Only one device affected: Check that device’s DNS and network settings.
- Only one website affected: The domain’s DNS configuration may be incorrect.
If your internet connection works normally on another network, focus on the original network before changing your computer’s settings.
2. Restart Your Router and Computer
Temporary router or network problems can sometimes interrupt DNS communication.
Try this simple restart:
- Turn off your router and modem, if you have separate devices.
- Wait approximately 30 seconds.
- Reconnect the power and allow the network to recover.
- Restart your computer and test the website again.
You can also disconnect and reconnect to Wi-Fi.
Don’t use your router’s factory-reset button. A normal restart is sufficient for this test and won’t erase your saved network configuration.
3. Test Your DNS Server with nslookup
Before changing DNS providers, check whether your configured resolver is answering requests.
On Windows, open Command Prompt or PowerShell and run:
nslookup google.com
This asks your configured DNS resolver to look up Google’s IP address.
Next, compare the result using Cloudflare’s public resolver:
nslookup google.com 1.1.1.1
If the first command times out but the second succeeds, your current DNS resolver or the network path to it may be experiencing problems.
If both fail, investigate your internet connection, firewall, or network restrictions.
If the response says the domain doesn’t exist, that’s a different DNS problem from a timeout.
The nslookup command is also useful for website administrators who need to verify DNS records.
4. Flush Your DNS Cache
Your computer temporarily stores DNS lookup results to speed up future requests.
Sometimes, outdated cached information contributes to connection problems.
On Windows:
Open Command Prompt and run:
ipconfig /flushdns
Windows should confirm that the DNS resolver cache was cleared.
On macOS:
Open Terminal and run:
sudo dscacheutil -flushcache
Then:
sudo killall -HUP mDNSResponder
Enter your administrator password if prompted.
Afterward, reopen your browser and test the website.
Flushing your DNS cache is generally safe, but it won’t fix an unavailable upstream DNS server or incorrect records on the website owner’s nameservers.
5. Change Your DNS Server
If your current DNS resolver is unavailable, switching to a trusted public DNS service may restore website access.
Two commonly used options are:
| Provider | Primary DNS | Secondary DNS |
|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
| Google Public DNS | 8.8.8.8 | 8.8.4.4 |
Change DNS on Windows 11
- Open Settings → Network & internet.
- Select your active Wi-Fi or Ethernet connection.
- Find DNS server assignment and click Edit.
- Change the setting from Automatic to Manual.
- Enable IPv4 and enter your preferred and alternate DNS addresses.
- Save the changes and test your connection.
Change DNS on macOS
- Open System Settings → Network.
- Select your active network connection.
- Click Details → DNS.
- Add your preferred DNS server addresses.
- Apply the changes and test the website again.
Record your previous settings so you can restore them if necessary.
If your device belongs to a company or school, contact the network administrator before changing DNS settings. Public resolvers may not work with private internal domains.
6. Check VPN, Proxy, and Security Software
VPN services, proxy configurations, and security applications can affect DNS resolution.
For example, a VPN may use its own DNS servers. If that connection becomes unavailable, website lookups may fail.
Check whether:
- Your VPN connection is operating correctly.
- Your device has an unexpected proxy configuration.
- Security software logs show DNS requests being blocked.
- Browser Secure DNS settings conflict with your network configuration.
If you’re using a personal VPN, test another permitted VPN location or reconnect the service.
Avoid disabling your firewall or antivirus protection. Review blocking rules and diagnostic logs instead.
On managed devices, ask your administrator before modifying VPN, proxy, or security settings.
7. Update Network Software or Contact Your ISP
If the error continues, check for operating system updates and network adapter problems.
Windows users can run the built-in network troubleshooter and review network adapter updates through Device Manager.
You can also check your configured DNS servers using:
ipconfig /all
Look for the DNS Servers entries associated with your active network adapter.
If multiple devices experience the problem and public DNS resolvers are also unreachable, your ISP may need to investigate.
When contacting support, explain which websites fail, which devices are affected, and whether the same connection works through another network.
These details can help identify the problem faster.
What If You Own the Website?
If visitors report DNS errors for a domain you manage, the issue may be with your domain configuration rather than their computers.
Check the following:
- Domain registration: Confirm your domain hasn’t expired.
- Nameservers: Make sure your registrar points to the correct authoritative DNS servers.
- DNS records: Verify the required A, AAAA, or CNAME records.
- DNSSEC: Check for incorrect DNSSEC configuration after changing DNS providers.
- Recent changes: Allow appropriate time for cached DNS responses to expire.
You can use nslookup or an online DNS lookup tool to compare results from multiple resolvers.
If your domain uses Cloudflare, review its DNS dashboard and confirm that the necessary records exist.
DNS Server Not Responding vs Other Connection Errors
Different connection errors can look similar but require different solutions.
| Error | Meaning |
|---|---|
| DNS Server Not Responding | A configured DNS resolver isn’t responding to requests |
| DNS_PROBE_FINISHED_NXDOMAIN | DNS resolution indicates that the requested domain doesn’t exist |
| ERR_CONNECTION_RESET | An established or attempted network connection was unexpectedly reset |
If your browser reports a reset rather than a DNS lookup failure, follow our ERR_CONNECTION_RESET troubleshooting guide instead.
If your website loads with an HTTPS security error rather than a DNS issue, our ERR_SSL_VERSION_OR_CIPHER_MISMATCH troubleshooting guide explains how to identify and fix SSL certificate, TLS protocol, and encryption compatibility problems.
Encountering DNS errors while accessing a website? Check out our guide on how to fix the DNS_PROBE_FINISHED_NXDOMAIN error to resolve domain name resolution issues and get back online.
Frequently Asked Questions
Common causes include internet connectivity problems, unavailable DNS resolvers, incorrect network settings, or interference from VPN and security software.
Both are established public DNS resolver services. However, they have different privacy policies, and changing providers may affect filtering or internal network services.
It can resolve temporary router and connectivity problems. However, it won’t repair incorrect domain records or a persistent ISP outage.
Not necessarily. Clearing DNS cache removes stored lookup results. It’s primarily a troubleshooting step, not a guaranteed internet speed improvement.
Conclusion
The DNS server not responding error doesn’t necessarily mean your internet connection is completely down. It often indicates a problem with how your device communicates with its DNS resolver.
Start by checking your connection and restarting your network equipment. If the issue persists, test your resolver, flush cached DNS information, and review your DNS settings.
The best approach is to identify where DNS resolution is failing before making changes to your network configuration.