DNS Server Not Responding? Causes and Fixes

If you see “DNS server not responding,” your device could not get a usable reply from the service that looks up website names, such as example.com, as internet addresses. Check whether the problem affects one device or your whole network, then work through the fixes below; restarting the router or correcting a device’s DNS settings often resolves a temporary fault.

What the error means

DNS, or the Domain Name System, translates human-readable domain names into IP addresses that computers use to connect. When a browser reports that a DNS server is not responding, it does not necessarily mean the website is down, your internet connection is completely unavailable, or the server itself has failed. The lookup may have timed out, been blocked, or failed somewhere between your device and the DNS resolver.

A DNS resolver is commonly provided by your internet service provider, though a device, router, VPN, or network administrator may direct requests elsewhere. The message can appear in a browser or in a computer’s network troubleshooter. The exact wording varies, and it describes a failed lookup rather than identifying its cause.

How to narrow down the cause

First, determine the scope. Try opening more than one familiar website, and see whether other devices on the same Wi-Fi can browse. If only one site fails, the problem may be that site, its domain configuration, or a cached result. If every site fails on one device but other devices work, focus on that device. If all devices fail on the same network, check the router, modem, and internet service.

One site, one device: Try another browser or network and check whether the address was typed correctly.
Many sites, one device: Look at that device’s connection, DNS settings, VPN, proxy, or security software.
Many devices on one network: Restart network equipment and check for an internet-provider outage.
Wi-Fi connected, no sites load: The Wi-Fi link may be working while the router’s internet connection or DNS service is not.

If practical, switch the affected device briefly to a different connection, such as a mobile hotspot. A successful lookup on the alternative connection points toward the original network or its DNS configuration, although it does not prove which component is at fault.

Fixes to try in order

Check the connection. Confirm Wi-Fi is connected to the intended network, or check the Ethernet cable. Open a few sites and check another device before changing settings.
Restart the network equipment. Use the router or modem’s normal restart procedure; if the devices are separate, restart both. Allow them time to reconnect. A restart can clear a temporary fault, but it will not fix an outage or incorrect configuration.
Restart the affected device. This can refresh its network connection. If the issue began after enabling a VPN or proxy, disconnect it temporarily to test whether it is involved. Restore it afterward if needed.
Run the operating system’s network troubleshooter. On Windows, use the network troubleshooting option in Settings. On macOS, check Network settings and the connection status. Menu labels can change between releases, so use the settings search if necessary.
Refresh the DNS cache. A device may retain an outdated lookup. Windows users can open Command Prompt and run ipconfig /flushdns. On macOS, DNS cache commands can vary by release; restarting is a straightforward alternative if you are unsure. Do not run commands from untrusted instructions.
Check DNS configuration. If the device is set to obtain DNS automatically, restore that setting if it was changed unexpectedly. On a managed work or school network, ask its administrator before editing it. A manually entered address can be mistyped or no longer available.
Contact your provider or network administrator. If multiple devices remain affected after a restart, ask whether there is an outage or a router-side issue. Provide the time the problem began and whether other networks work.

Changing DNS servers: when it helps

Some people test a different public DNS resolver when their provider’s resolver appears unavailable or unreliable. A device or router may allow you to enter primary and secondary DNS addresses, but the addresses depend on the resolver you choose. Use the provider’s own published documentation and enter them carefully. Do not copy addresses from an unfamiliar website.

Changing DNS can help distinguish a resolver problem from other connection problems, but it is not a universal repair. It will not restore a disconnected modem, fix a damaged cable, or make an offline website available. A resolver change may also conflict with parental controls, workplace filtering, or network policies. If the change does not help, restore the previous automatic or administrator-provided settings.

Common misconceptions and cautions

“Wi-Fi connected” only means the device has joined a wireless network; it does not guarantee that the router has working internet access. Likewise, a DNS error does not by itself show that your device has malware or that a website is unsafe. Avoid downloading “DNS repair” utilities or disabling a firewall as a first response. These steps can introduce risk without addressing the cause.

Clearing the DNS cache removes stored name-lookup information, not personal files or browsing history. Resetting all network settings is more disruptive: it can remove saved Wi-Fi details, VPN settings, or other network configuration. Reserve broad resets for cases where simpler checks fail, and make sure you can restore required settings first.

Frequently Asked Questions

Why does my phone say the DNS server is not responding?
Its current Wi-Fi or mobile network may not be completing DNS lookups. Check whether other devices on the same Wi-Fi work, toggle the phone’s connection off and on, and restart the router if the whole network is affected.

Does this error mean my internet is down?
Not always. Your device may be connected to Wi-Fi while the router has lost its internet connection, or only DNS lookups may be failing. Testing another device or network helps separate these cases.

Should I change my DNS server?
Only if you have a reason to test a different resolver and can use its verified settings. First check for a network outage and restart the equipment. Changing DNS cannot repair every kind of internet failure.

Will flushing DNS delete my data?
No. Flushing the DNS cache clears stored website-name lookup results so the device can request them again. It does not erase documents, accounts, or browser history.

Why does the error happen only on one website?
The site or its domain records may have a temporary issue, or your device may have a stale lookup. Check the address, try another browser or network, and wait before making broad changes to your network.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →