A “DNS server not responding” error usually means Windows 11 did not get a usable answer from the DNS resolver configured for your connection. It does not automatically mean your WiFi is bad. Check another device first, restart the PC and router, pause any VPN or custom proxy, flush the DNS cache, and then test a known public DNS service. Use Windows Network reset only after those checks.
The order matters. A full reset can remove network adapters and VPN settings, while a two-minute test may show that the problem is really your router, internet provider, or one browser.
Find out where the DNS failure is
DNS turns a name such as example.com into the numeric address a device needs to reach the site. When that lookup fails, Windows may still show that it is connected to WiFi even though pages do not open.
| What you see | Most likely area to check | Best first move |
|---|---|---|
| Only one website fails | The website, browser, extension, or cached record | Try another site and another browser before changing Windows |
| Only one Windows 11 PC fails | That PC’s cache, DNS setting, VPN, proxy, or adapter | Restart the PC, pause VPN, and flush DNS |
| Every device on the same network fails | The router, internet provider, or provider DNS | Restart the router and check the provider’s outage page |
| Ethernet works but WiFi does not | The WiFi profile, wireless adapter, or router radio | Forget and reconnect to the WiFi network |
| The problem appears only while a VPN is connected | The VPN’s DNS or routing policy | Disconnect the VPN for one test |
Use a phone on the same WiFi as a quick comparison. If the phone also cannot open several well-known sites, do not spend an hour changing settings on the PC. Start with the router and provider. If every other device works, follow the device-focused steps below. Our guide for WiFi failing on only one device covers adapter, saved-network, and device-specific causes in more detail.
1. Restart the PC, router, and connection
Save your work and restart Windows. A shutdown followed by a quick power-on can behave differently when Fast Startup is enabled, so use Restart from the power menu for this test.
If several devices have the same problem, restart the modem or gateway and router. Unplug their power, wait about 30 seconds, reconnect the modem or gateway first, and give it time to come online. Then reconnect a separate router. Do not press a recessed factory-reset button. That erases settings and is not part of a normal restart.
Microsoft’s Windows connection troubleshooting guide also recommends testing the same network with another device. That single comparison separates a local Windows problem from a network-wide failure.
2. Pause VPN and check the proxy setting
A VPN can supply its own DNS servers and routes. Disconnect it temporarily, close and reopen the browser, and test two unrelated websites. If pages load, reconnect the VPN and check for an app update or contact its support team. You do not need to uninstall the VPN for this test.
Next, open Settings > Network & internet > Proxy. A home PC normally uses automatic detection unless you deliberately configured a script or manual proxy. Do not remove a work or school proxy that your organization requires. Microsoft’s Windows proxy guide explains what the automatic, script, and manual options do.
If one browser fails while another works, the Windows DNS server may be fine. Check that browser’s Secure DNS setting, extensions, and proxy configuration before resetting the whole PC.
3. Reconnect to the network
For WiFi, make sure you know the network password. Open Settings > Network & internet > Wi-Fi > Manage known networks, choose the network, and select Forget. Reconnect from the taskbar network menu and enter the password again.
For Ethernet, unplug and reconnect the cable. You can also open Settings > Network & internet > Advanced network settings, disable the active adapter, wait a few seconds, and enable it again. Reconnecting lets Windows request fresh network information from the router, including the DNS server addresses supplied by DHCP.
4. Flush the Windows DNS cache
Windows stores recent DNS answers so it does not need to repeat every lookup. A failed or outdated answer can remain in that cache. Clearing it does not delete browser history, saved WiFi networks, or passwords.
- Select Start, type Terminal, and open Windows Terminal.
- Enter the command below and press Enter.
ipconfig /flushdnsWindows should report that it successfully flushed the DNS Resolver Cache. Close and reopen the browser, then test again. Microsoft’s ipconfig reference describes /flushdns as a troubleshooting command that discards cached DNS entries, including negative results.
5. Test the current resolver against a public one
A simple comparison can show whether the configured DNS server is the weak link. Open Windows Terminal and run these commands one at a time:
nslookup example.com
nslookup example.com 8.8.8.8The first command asks the DNS server Windows is already using. The second asks Google Public DNS directly. The Microsoft nslookup reference confirms that a second argument selects the DNS server for that lookup.
| Result | What it suggests | Next step |
|---|---|---|
| Both commands return addresses | DNS is responding now | Check the browser, extension, proxy, or the one site that still fails |
| The first fails and the second succeeds | Your configured resolver may be unavailable or misconfigured | Temporarily change to a complete public DNS pair |
| Both time out | The problem is broader than one DNS provider | Check the router, firewall, VPN, adapter, and ISP connection |
| The response says the domain does not exist | The requested name may be wrong or its DNS records may be missing | Retype the address and test another established domain |
Use example.com exactly for the comparison. It is a stable test name and avoids confusing a single site’s outage with a general DNS failure.
6. Change DNS only when the test points to it
Write down the current setting before changing it. In Windows 11, open Settings > Network & internet, select the active WiFi or Ethernet connection, find DNS server assignment, and choose Edit. Select Manual, turn on IPv4, and enter both addresses from one provider.
- Google Public DNS preferred:
8.8.8.8 - Google Public DNS alternate:
8.8.4.4
Do not use 8.8.8.8 as the preferred address and an unrelated provider as the alternate while troubleshooting. A matched pair makes the test easier to interpret. Google’s Public DNS setup page publishes both addresses and recommends configuring at least two different addresses from its service.
Save the setting, flush the DNS cache again, and test several sites. If nothing changes, return DNS server assignment to Automatic (DHCP). A public resolver is a diagnostic option, not a cure for a broken WiFi link or an ISP outage. Changing it may also bypass DNS-based parental controls or filtering supplied by your router or provider.
Microsoft’s network settings guide for Windows explains automatic and manual DNS assignment, including the DNS over HTTPS choices available in Windows 11.
7. Reset the network commands in the right order
Use this group only if the earlier checks failed. Right-click Start, choose Terminal (Admin), approve the Windows prompt, and run each command on its own line:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns| Command | What it changes | What to expect |
|---|---|---|
netsh winsock reset | Returns the Winsock catalog to its default state | Restart Windows after the sequence |
netsh int ip reset | Resets TCP/IP settings | Custom network settings may need to be entered again |
ipconfig /release | Releases the current DHCP address | The PC disconnects briefly |
ipconfig /renew | Requests fresh address and network information | The router must have working DHCP |
ipconfig /flushdns | Clears cached DNS answers | Saved networks and passwords stay in place |
Restart the PC after the commands finish. Microsoft lists these commands in the same order in its Windows connection troubleshooting instructions. If ipconfig /renew cannot obtain an address, the problem is no longer just DNS. Check the adapter, router, or provider connection.
8. Use Network reset as the last Windows step
Open Settings > Network & internet > Advanced network settings > Network reset. Select Reset now only after saving your work and noting any custom network settings.
Network reset removes installed network adapters and their settings, then reinstalls the adapters after Windows restarts. Microsoft warns that you may need to reinstall VPN clients or virtual networking software afterward. It can also change known connections to the public network profile. This is why it belongs near the end of the checklist.
When the problem belongs to the router or ISP
Stop changing the PC when every device fails on the same connection. Check the modem or gateway lights and your provider’s outage page over cellular data. If the provider-supplied DNS fails while a public resolver works, report the time of the test and the two nslookup results. If both resolvers time out, tell support that the failure affects several devices and survives a router restart.
A connected WiFi icon only confirms the local wireless link. It does not prove that the router has a working internet connection. The broader WiFi connected but no internet checklist helps separate modem, router, ISP, and device failures.
Questions people ask about DNS errors
How do I reset DNS on Windows 11?
Open Windows Terminal, run ipconfig /flushdns, and reopen the browser. That clears the local DNS cache. It does not change the DNS provider. If the configured resolver is unavailable, test it with nslookup and then change the DNS server assignment only if the comparison supports that step.
Why did DNS suddenly stop working?
Common causes include a temporary router or ISP resolver outage, a stale cached response, a VPN or proxy change, incorrect manual DNS addresses, or a damaged Windows network configuration. Testing another device and comparing the default resolver with a public one narrows the cause faster than guessing.
Is it safe to use Google Public DNS?
Google Public DNS is a documented public resolver and can be useful for comparison or continued use. Changing DNS means that provider receives your DNS queries, so review its privacy information and remember that the change may bypass filtering supplied by your ISP or router. Record the original setting so you can return to Automatic (DHCP).
Should I disable IPv6 to fix the error?
Do not disable IPv6 as an early troubleshooting step. It changes more than DNS and can hide a faulty router advertisement or resolver setting instead of identifying it. First test another device, clear the cache, compare resolvers, and return any incorrect manual DNS entry to Automatic. Escalate a repeatable IPv6-only failure to the router vendor or ISP with the test results.
