The DNS server not responding message in Windows 11 usually means your PC could not get a usable answer from the service that translates website names into IP addresses. The problem may be a stale local cache, an unavailable DNS resolver, a VPN or proxy conflict, incorrect manual settings, a router fault, or a wider internet outage.

Do not change DNS immediately just because the troubleshooter mentions it. First determine whether every device is affected, whether only one website fails, and whether Windows can reach its configured DNS server. That short diagnosis prevents unnecessary driver removals, router resets, and permanent changes to a work or school network.

This guide applies to Windows 11 Home and Pro on Wi-Fi or Ethernet. Menu wording can vary by Windows release, device manufacturer, and organization policy. The instructions and official sources were reviewed on August 20, 2026.

Quick Answer

Test another website and another device first. Restart the affected browser and PC, then restart the modem and router if multiple devices fail. Run nslookup microsoft.com to check DNS directly. If only the PC is affected, run the Windows 11 Network and Internet troubleshooter, disconnect an optional VPN, check the proxy, and use ipconfig /flushdns. Restore DNS to Automatic (DHCP) before testing one complete public DNS pair. Save Network reset for last.

Key Takeaways

  • DNS translates names such as microsoft.com into numeric addresses; it does not create the internet connection itself.
  • If every device on the same network fails, focus on the router, modem, ISP, or DNS service—not only Windows.
  • nslookup tests DNS without relying on the Windows DNS client cache, making it more useful than guessing from a browser error.
  • ipconfig /flushdns removes cached DNS entries; it does not change your DNS provider.
  • Use either the complete Cloudflare pair or the complete Google pair for a test—do not mix providers.
  • Do not override company, school, parental-control, filtering, or VPN DNS settings without approval.
  • Network reset removes and reinstalls network adapters and resets their settings, so it belongs at the end.
Before changing anything: record the current DNS setting, save your Wi-Fi password, and note any required VPN, proxy, static IP, or organization configuration. On a managed work or school computer, contact IT before changing DNS or removing network software.

What “DNS Server Not Responding” Actually Means

When you enter a website name, Windows asks a DNS resolver for the corresponding IP address. Home networks normally receive DNS server addresses automatically from the router through DHCP. A VPN, browser, security product, workplace policy, or manual Windows setting can use a different resolver.

The error means a DNS request did not produce a usable response in time. It does not prove that the DNS server itself is broken. The PC may have no valid IP address, the router may be offline, a VPN may be blocking traffic, a firewall may be filtering DNS, or the requested domain may simply be unavailable.

What you observe Likely area Best first action
Only one Windows 11 PC fails PC cache, VPN, proxy, DNS setting, or adapter Run nslookup, then follow the PC fixes
Every device on the network fails Router, modem, ISP, or upstream DNS Restart network equipment and check the ISP
Only one website fails Website, domain record, browser, or filtering Test unrelated sites and another device
nslookup succeeds but the browser fails Browser Secure DNS, extension, proxy, VPN, or app Test another browser and inspect app-specific settings
Public sites work but internal names fail Work/school VPN, DNS suffix, or internal resolver Reconnect the required VPN and contact IT
IP address starts with 169.254 No valid DHCP lease Fix the IP/router connection before changing DNS

Diagnose DNS in Three Minutes

1. Check the scope

Open two unrelated websites and test another app. Then temporarily turn off cellular data on a phone and test that phone on the same Wi-Fi. If the phone and PC both fail, the problem is less likely to be a Windows-only DNS cache.

2. Check the active network configuration

Open Command Prompt and run:

ipconfig /all

Find the active Wi-Fi or Ethernet adapter. Confirm that it has an IPv4 address, a Default Gateway, and one or more DNS Servers. Ignore disconnected Bluetooth, virtual-machine, and VPN adapters. An IPv4 address beginning with 169.254 usually means the PC did not receive a valid DHCP lease, so repair the network connection before treating the symptom as DNS-only.

3. Query DNS directly

Run:

nslookup microsoft.com

A successful result normally shows the DNS server used and one or more addresses for the domain. A timeout or “server failed” result points toward the configured resolver, the path to it, or filtering. An NXDOMAIN or “non-existent domain” result for only one name may indicate that the name is wrong, its record is missing, or a filter is blocking it.

Why this test matters: nslookup does not depend on the Windows DNS client cache. If it succeeds while one browser still fails, avoid resetting the whole network first; investigate that browser, its Secure DNS setting, extensions, proxy, VPN, or security filter.
Do not use a raw IP address in the browser as definitive proof: modern HTTPS sites, shared hosting, and content delivery networks depend on the requested hostname. A numeric address can fail even when the internet connection and DNS are otherwise healthy.

Fix 1: Restart the Affected App, Network Connection, and PC

Begin with the lowest-risk refresh. It clears temporary browser and adapter states without deleting saved networks or changing DNS providers.

  1. Close every browser window and the app showing the error.
  2. Turn Wi-Fi off from Quick Settings, wait about 10 seconds, and turn it back on. For Ethernet, disconnect and reconnect the cable if it is safe to do so.
  3. Test two unrelated websites.
  4. If the error remains, save your work and choose Start → Power → Restart.
  5. After Windows starts, run nslookup microsoft.com again.

Use Restart rather than only shutting the lid or putting the PC to sleep. If the problem affects one browser only, test a private window and a second browser before changing Windows networking.

Fix 2: Restart the Modem and Router and Check the ISP

Use this step early when several devices fail or when the configured DNS server is the router's local address, such as 192.168.1.1. The router may be forwarding DNS requests to an unavailable ISP resolver.

  1. Unplug the router from power.
  2. Unplug the modem. If you have one combined gateway, unplug that single device.
  3. Wait at least 30 seconds. Do not press the Reset pinhole.
  4. Reconnect the modem first and wait for its normal connection lights.
  5. Reconnect the router and wait a few minutes.
  6. Reconnect the PC and phone, then test again.

If all devices remain offline, use cellular data to check the ISP's official outage page or app. A line outage, failed modem, suspended account, or damaged router cannot be fixed by repeatedly flushing the Windows DNS cache.

Restart is not factory reset: holding the router's Reset button can erase the Wi-Fi name, password, ISP login, DNS choices, parental controls, and other settings. Only perform a factory reset with the router manufacturer or ISP instructions and a configuration backup.

Fix 3: Run the Windows 11 Network and Internet Troubleshooter

Microsoft recommends starting with the automated Network and Internet troubleshooter in the Get Help app on Windows 11. It can identify common adapter, gateway, IP, and DNS configuration problems.

  1. Open Start and search for Get Help.
  2. Open the app and search for network troubleshooter or DNS server not responding.
  3. Choose the symptom that matches your connection and allow the diagnostics to run.
  4. Apply only changes you understand.
  5. Restart if requested, then retest with nslookup and a browser.

You may also see troubleshooting options under Settings → System → Troubleshoot → Other troubleshooters, depending on the Windows release. A managed PC may report an organization-controlled setting that only IT can change.

Fix 4: Forget and Reconnect to Wi-Fi

A damaged or outdated Wi-Fi profile can preserve old network information. This step affects only the selected wireless network; skip it on Ethernet.

  1. Make sure you know the current Wi-Fi password.
  2. Open Settings → Network & internet → Wi-Fi → Manage known networks.
  3. Select the affected network and choose Forget.
  4. Return to the Wi-Fi list, select the network, and enter its password.
  5. Run ipconfig /all and nslookup microsoft.com again.

If the PC shows Connected, no internet after reconnecting, use our separate Windows 11 Wi-Fi connected but no internet guide for DHCP, gateway, captive portal, and driver checks beyond DNS.

Fix 5: Test Without an Optional VPN, Manual Proxy, or Browser Secure DNS

A VPN can supply its own DNS resolver and block normal traffic if its tunnel or kill switch fails. A manual proxy or browser-level encrypted DNS setting can also make one app fail while Windows itself resolves names correctly.

Temporarily disconnect an optional VPN

  1. Open Settings → Network & internet → VPN.
  2. Disconnect the active VPN for a short test; do not delete its profile.
  3. Run nslookup microsoft.com and test the browser.
  4. If DNS works only without the VPN, update or repair the VPN through its official provider.

Check the Windows proxy

  1. Open Settings → Network & internet → Proxy.
  2. For a normal home connection, leave Automatically detect settings enabled.
  3. If Use a proxy server is enabled and you did not configure it, record its details and turn it off temporarily.
  4. Test again.

Check browser Secure DNS only if the browser alone fails

Browsers may call the option Secure DNS, DNS over HTTPS, or Use secure DNS. Set it back to its default or current-provider mode for a test rather than selecting random providers. Browser menu names change frequently, so use that browser's official help page for the current path.

Work and school devices: VPN, proxy, encrypted DNS, certificates, and security agents may be required. Do not bypass them or disable Microsoft Defender Firewall. Reconnect the required configuration and contact IT.

Fix 6: Flush the Windows DNS Cache

The Windows DNS client cache can contain an expired or negative entry. Microsoft documents ipconfig /flushdns specifically for discarding dynamically added and negative cache records during name-resolution troubleshooting.

  1. Open Start and type Command Prompt.
  2. Select Run as administrator and approve the prompt.
  3. Run:
ipconfig /flushdns
  1. Look for a message confirming that the DNS Resolver Cache was flushed.
  2. Close and reopen the affected browser or app.
  3. Run nslookup microsoft.com and test the failed name again.

Flushing the cache does not erase browser history, passwords, bookmarks, personal files, or the configured DNS server. It also does not repair an offline router or unavailable resolver.

Do not run it repeatedly: one successful flush is enough for the test. If the error immediately returns, move to configuration and connectivity checks instead of creating a downloaded BAT file.

Fix 7: Renew DHCP and Reset Winsock and TCP/IP

Use these Microsoft-recommended commands when the PC has an invalid lease, DNS servers were supplied incorrectly by DHCP, or the Windows network stack is damaged. Save online work first: releasing the address temporarily disconnects DHCP-configured adapters.

  1. Open Command Prompt as administrator.
  2. Run each command in this order:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
  1. Read the output for errors instead of closing the window immediately.
  2. Restart Windows.
  3. Run ipconfig /all and confirm the active adapter has a valid address, gateway, and DNS server.
  4. Test DNS again.

ipconfig /renew applies to adapters configured to obtain an address automatically. If it cannot contact a DHCP server, focus on the router, cable, Wi-Fi connection, or organization network. Do not invent a static IP address to work around the failure.

Use the commands exactly as shown: do not download “DNS repair,” registry cleaner, Winsock optimizer, or network booster scripts. Unknown scripts can change firewall, proxy, Hosts, and adapter settings without explaining how to undo them.

Fix 8: Restore DNS Server Assignment to Automatic

An old manual DNS address may belong to a resolver that is offline, blocked, or no longer appropriate for the current network. Returning to Automatic allows DHCP to obtain DNS settings from the router or access point.

  1. Open Settings → Network & internet.
  2. Select the active Wi-Fi connection or Ethernet.
  3. Find DNS server assignment and select Edit.
  4. Record any existing manual addresses before changing them.
  5. Choose Automatic (DHCP) and select Save.
  6. Disconnect and reconnect, or restart the PC.
  7. Run ipconfig /all to confirm the assigned DNS servers, then test.

Some Windows builds place related controls under the network's hardware properties or IP assignment. Microsoft recommends DHCP for normal networks because it supplies compatible IP and DNS settings automatically.

Static networks are different: if your ISP, router administrator, workplace, lab, or server environment gave you specific addresses, do not replace them. Verify the required values with the administrator.

Fix 9: Test One Known Public DNS Pair

If the PC has a valid IP and gateway but the automatically assigned resolver keeps timing out, a temporary public DNS test can isolate the problem. Record the current setting first so you can restore it.

Provider Preferred IPv4 DNS Alternate IPv4 DNS
Cloudflare 1.1.1.1 1.1.1.1 1.0.0.1
Google Public DNS 8.8.8.8 8.8.4.4
  1. Open Settings → Network & internet and select the active adapter.
  2. Next to DNS server assignment, select Edit.
  3. Choose Manual and turn on IPv4.
  4. Enter one complete pair from the table. Do not use one Cloudflare address and one Google address.
  5. If Windows offers DNS over HTTPS and recognizes the provider, use the automatic template if you want encrypted DNS. Do not invent a template URL.
  6. Select Save, reconnect, and run ipconfig /flushdns.
  7. Test nslookup microsoft.com and several unrelated sites.
  8. If there is no improvement, restore Automatic (DHCP).

Changing DNS transfers name queries to the selected provider. It is not a guaranteed speed boost, does not fix a dead modem or weak Wi-Fi, and may bypass router-based parental controls or local-device names. Review the provider's privacy terms before leaving the change in place.

Do not override managed DNS: public resolvers may be blocked on work, school, hotel, filtered, or VPN networks. Internal company names may stop resolving if you replace the organization resolver.

Fix 10: Restart and Repair the Network Adapter

If DNS fails only on this PC across several trusted networks, restart the active adapter and inspect its driver. Do not disable every item under Network adapters.

  1. Right-click Start and open Device Manager.
  2. Expand Network adapters.
  3. Identify the active Wi-Fi or Ethernet adapter. Avoid Bluetooth, VPN, Hyper-V, and other virtual adapters.
  4. Right-click the active adapter and choose Disable device.
  5. Wait about 10 seconds, right-click it again, and choose Enable device.
  6. Restart the PC and test.

If the problem followed a driver update

  1. Open the adapter's Properties → Driver tab.
  2. If Roll Back Driver is available and the timing matches, use it and restart.

If you need a new driver

Download the Windows 11 network driver for the exact PC model from the computer manufacturer's official support page. Save the installer before uninstalling the current driver, especially if the PC may lose all connectivity. Avoid generic third-party driver-updater programs.

Fix 11: Check the Router's DNS and Firmware

If every device receives the same DNS errors, or devices work only after manually selecting a public resolver, the router may be advertising an unavailable DNS server or failing to forward queries.

  1. Open the router's official manual or ISP support instructions.
  2. Sign in only through the router's known local address or official management app.
  3. Record the current Internet, DHCP, and DNS values before changing anything.
  4. Confirm that DHCP is enabled for a normal home network and that DNS addresses are valid.
  5. Check the router manufacturer's official site for firmware for the exact model and hardware revision.
  6. If the router is ISP-managed, contact the ISP rather than forcing unsupported firmware or DNS values.

Do not follow a random screenshot for another router model. Incorrect WAN, VLAN, PPPoE, DHCP, or DNS settings can disconnect the entire home. Do not expose remote router administration to the internet just to troubleshoot DNS.

Security check: if router DNS values change again after you correct them, update the router firmware, use a strong unique administrator password, disable unnecessary remote administration, and ask the manufacturer or ISP for help. Do not enter banking or email credentials through unexpected router warnings.

Fix 12: Use Network Reset as the Last Resort

Microsoft says Network reset should be one of the last steps. It removes installed network adapters and their settings, restarts the PC, reinstalls the adapters, and returns networking settings to defaults.

Before Network reset: save the Wi-Fi password and any required DNS, static IP, proxy, or VPN details. You may need to reinstall VPN clients, Hyper-V virtual switches, virtual-machine adapters, packet-capture tools, and other networking software.
  1. Open Settings → Network & internet → Advanced network settings.
  2. Select Network reset.
  3. Read the warning, then select Reset now → Yes.
  4. Allow Windows to restart.
  5. Reconnect to the correct network and choose the appropriate network profile.
  6. Reinstall only trusted networking software that you actually need.
  7. Run ipconfig /all and nslookup microsoft.com again.

Network reset does not delete personal documents, but it can disrupt remote work and specialized network configurations. Do not use it on a managed computer without IT approval.

If Only One Website or App Still Fails

If nslookup microsoft.com and other unrelated names work, the entire DNS system is probably not down. Narrow the problem before changing more settings.

  • Check the spelling of the domain.
  • Test the site in another browser and on another network.
  • Check the service's official status page.
  • Temporarily disable only the extension suspected of filtering that site.
  • Confirm that the PC's date, time, and time zone are correct.
  • If a work or school name fails, reconnect the required VPN and contact IT.
  • If the domain returns NXDOMAIN everywhere, its DNS record may be missing or expired; Windows resets cannot recreate it.

Do not disable Microsoft Defender Firewall or antivirus protection permanently to reach one site. If browser pages display fake infection warnings or demand a download, follow our guide to removing fake virus pop-ups safely instead of installing the advertised “DNS repair” tool.

What Not to Do

  • Do not assume every connection failure is DNS just because a troubleshooter mentions it.
  • Do not mix primary and alternate addresses from different public DNS providers.
  • Do not disable IPv6 as a generic fix; modern networks and services may depend on it.
  • Do not edit the Registry, Hosts file, DNS Client service, or firewall rules without a specific diagnosis and rollback plan.
  • Do not install DNS boosters, registry cleaners, driver packs, or downloaded repair scripts.
  • Do not factory-reset the router before saving its ISP and Wi-Fi configuration.
  • Do not override workplace, school, VPN, parental-control, or filtered DNS policies.
  • Do not run Network reset repeatedly; one reset is enough to test default settings.

When to Contact the ISP, Router Maker, or IT

Contact Contact them when Useful details
Internet service provider All devices fail, modem lights show a fault, or ISP DNS repeatedly times out Outage start time, modem lights, DNS server shown by ipconfig /all, and multi-device tests
Router manufacturer The router advertises invalid DNS, changes do not persist, or firmware is unavailable Exact model, hardware revision, firmware version, and saved configuration
PC manufacturer The adapter fails on several networks, disappears, or reports a Device Manager error PC model, Windows build, adapter name, driver version, and error code
Work or school IT Internal names, required VPN, proxy, certificate, or managed DNS fails Exact failed name, time, network, VPN state, and nslookup result

For more safety-first repair articles, browse the ACSNETWORLD Windows guides.

Read Next Windows 11 Wi-Fi Connected but No Internet: 12 Safe Fixes
Related Security Guide Remove Fake Virus Pop-Ups From Windows 11 Safely

Frequently Asked Questions

Why does Windows 11 say the DNS server is not responding?

Windows did not receive a usable DNS answer in time. The cause can be an unavailable resolver, stale cache, incorrect manual setting, VPN or proxy conflict, router fault, missing internet connection, or filtering. Test another device and run nslookup before changing providers.

What command fixes DNS in Windows 11?

ipconfig /flushdns clears the Windows DNS client cache and is useful for stale or negative cached entries. It is not a universal repair: it cannot restore an offline router, failed ISP, invalid DHCP lease, blocked VPN, or unavailable DNS server.

How do I know whether DNS is the real problem?

Run ipconfig /all to inspect the active adapter and nslookup microsoft.com to query DNS directly. Compare another website, app, device, and network. If only one site fails or nslookup succeeds, a full Windows DNS failure is less likely.

Should DNS be automatic or manual in Windows 11?

Automatic (DHCP) is the normal recommended choice because the router or network provides compatible IP and DNS settings. Manual DNS is appropriate when a trusted network administrator specifies it or when you intentionally test a known provider and understand how to restore the previous setting.

Is 1.1.1.1 or 8.8.8.8 better?

Both are established public DNS services, operated by Cloudflare and Google respectively. Neither is guaranteed to be fastest or best on every network. Test one complete pair, consider the provider's privacy terms and network policies, and return to Automatic if it does not solve the diagnosed problem.

Can a VPN cause DNS server not responding?

Yes. A failed VPN tunnel, kill switch, virtual adapter, or assigned DNS resolver can block queries. Disconnect an optional VPN temporarily to test, then update or repair it through the official provider. Do not remove a required work or school VPN without IT approval.

Does flushing DNS delete passwords or browser history?

No. ipconfig /flushdns clears the Windows DNS client resolver cache. It does not delete documents, Wi-Fi passwords, browser bookmarks, saved website passwords, or browsing history.

Will Network reset delete my files?

Network reset does not delete personal documents, but it removes and reinstalls network adapters and returns their settings to defaults. You may need to reconnect to Wi-Fi and reinstall or reconfigure VPN clients, virtual switches, and other networking software.

Official Sources

  1. Microsoft Support — Fix Wi-Fi connection issues in Windows
  2. Microsoft Support — Essential network settings and tasks in Windows
  3. Microsoft Support — Use a proxy server in Windows
  4. Microsoft Learn — ipconfig command reference
  5. Microsoft Learn — Troubleshooting DNS clients
  6. Cloudflare Documentation — Set up 1.1.1.1 on Windows
  7. Google for Developers — Configure Google Public DNS

Article Changelog

Created with a DNS-first diagnostic flow, 12 safety-ordered fixes, current Windows 11 paths, cache and DHCP commands, VPN and proxy checks, public DNS cautions, Network reset warnings, and official Microsoft, Cloudflare, and Google sources.
Advertisement