How to Fix DNS Server Not Responding: 9 Proven Steps

Seeing the “DNS server not responding” error when websites will not load? DNS translates a site name into the address your device needs to connect. A failure can come from one device, your router, your internet provider, or a DNS service. Follow these steps to fix a DNS server not responding error safely, starting with quick checks before changing network settings.

1. Check Whether the Problem Affects One Device or Everyone

Try opening a few different websites on the affected device. Then test another phone or computer on the same Wi-Fi. If only one device has the DNS error, focus on its network settings and cache. If every device is affected, the router, modem, internet connection, or provider’s DNS is more likely. Also try the affected device on mobile data or another network, if available.

2. Check for an Internet or Provider Outage

Look at your provider’s service-status page using mobile data, or contact its support line. If there is a local outage, changing DNS on your computer is unlikely to restore the connection. Check that the modem’s internet or WAN indicator is normal and that cables are firmly connected. A provider outage or line fault needs the provider’s attention.

3. Restart the Device and Network Equipment

Restart the computer or phone first. If the problem affects multiple devices and there is no reported outage, restart the modem and router using their power buttons or by unplugging them. Wait about 30 seconds before powering them back on, then allow several minutes for the connection to return. Avoid pressing the factory-reset button, which can erase your Wi-Fi name and settings.

4. Reconnect to Wi-Fi and Turn Off Conflicting Network Tools

Forget the Wi-Fi network on the affected device, reconnect, and carefully re-enter its password. If you use a VPN, security filter, custom DNS app, or parental-control service, temporarily pause it to test whether it is interfering with name lookups. Re-enable protection after testing. Do not disable security software on an unfamiliar or public network.

5. Flush the DNS Cache

A stale local DNS entry can prevent a device from reaching a site even after the underlying problem is fixed. On Windows, open Command Prompt as an administrator and run ipconfig /flushdns. On macOS, restart the Mac first; current macOS versions generally clear the resolver cache on restart. On phones, toggle Airplane Mode briefly or restart the device. Menu names and cache controls vary by operating system.

6. Renew the Device’s Network Connection

If your device received incomplete network settings, disconnect and reconnect to Wi-Fi. On Windows, you can open Command Prompt as an administrator and run ipconfig /release followed by ipconfig /renew. This requests a fresh local address from the router. Do not run commands on a managed work or school device unless your administrator permits it.

7. Check Automatic DNS Settings Before Changing Them

Most home networks should receive DNS settings automatically from the router or internet provider. Check whether a manually entered DNS address is outdated or mistyped. If you are unsure, set the device’s DNS option back to automatic and reconnect. On a work, school, or managed network, custom DNS may be required, so check with its administrator before changing it.

8. Test a Reputable Public DNS Provider

If your provider’s DNS appears to be the problem, you can test a reputable public DNS service on one device. For example, Cloudflare’s public resolver uses 1.1.1.1 and 1.0.0.1; Google Public DNS uses 8.8.8.8 and 8.8.4.4. Enter addresses only in the DNS settings for your device or router, and record the original settings so you can restore them. DNS providers have different privacy policies, and changing DNS does not encrypt all of your internet traffic. If the test does not help, switch back to automatic DNS.

9. Update Network Software and Escalate Carefully

Install pending operating-system and network-adapter updates from the device maker or operating system’s official update tool. Avoid third-party driver download sites. If the problem continues on every device after a router restart, contact your internet provider and report the error, when it started, and whether the modem shows a connection. If only one computer is affected, share its operating-system version and the troubleshooting steps you tried with the device maker or network administrator.

Frequently Asked Questions

What does “DNS server not responding” mean?

Your device could not get a response when asking a DNS resolver to look up a website’s address. The cause may be the device, router, provider, or DNS service.

Will changing DNS fix my internet connection?

It can help if the current DNS resolver is unavailable or misconfigured. It will not fix a disconnected modem, weak Wi-Fi signal, account issue, or broader provider outage.

Is it safe to flush DNS?

Yes. Flushing DNS removes temporary lookup records and does not delete personal files, saved passwords, or browsing history.

Should I change DNS on my router or just my computer?

Test on one device first. If that resolves the issue and you want the setting for every device, you can consider changing the router setting, but save the original values and check with your provider first.

Conclusion

When a DNS server is not responding, first identify whether one device or the whole network is affected. Check for an outage, restart equipment safely, refresh the device connection, and clear its DNS cache. Only test another DNS provider after those checks, and restore automatic settings if there is no improvement. This approach helps isolate the fault without unnecessary resets or risky downloads.