DNS troubleshooting guide

DNS Server Not Responding

DNS problems are sneaky because the network icon can look normal while websites still refuse to load. In plain terms, the laptop can often see the network just fine, but it cannot translate site names into the addresses it needs to actually reach them.

Quick answer

Check whether the problem is just name resolution or the whole connection

Quick answer

DNS errors usually mean the connection is partly alive but website name lookups are failing. Before changing DNS settings, check whether the problem affects one device or the whole network and whether restarting the router clears it.

Common causes

Common causes of DNS failures in Windows

Test name resolution and change one thing at a time

First confirm the PC is connected and has an address and gateway. If other devices also cannot browse, investigate the router or ISP before changing this PC. Keep a note of existing DNS settings so every experiment can be reversed.

  1. Open Command Prompt and run nslookup example.com. Note the responding server and whether an address is returned. A timeout differs from a single domain that does not exist; test a second familiar domain before diagnosing all DNS as broken.
  2. If ordinary browsing fails but lookups work, compare another browser. Browser secure-DNS settings, a proxy, VPN or extension may use a different path. On a personal PC, test a suspect extension or your optional VPN one at a time and restore it afterward. Do not bypass an organization's network controls.
  3. For possible stale Windows DNS entries, open Terminal as administrator and run ipconfig /flushdns. Reopen the browser and retry the same site. Flushing clears the local resolver cache; it cannot fix an unreachable DNS server or a broken internet connection.
  4. On a personal network that permits it, nslookup example.com 1.1.1.1 tests a public resolver without changing saved Windows settings. This sends that lookup to the specified resolver. If it works while the normal lookup consistently fails, investigate your configured DNS service. A timeout is inconclusive because some networks block outside DNS.
  5. If you previously entered manual DNS, open your active connection's properties under Settings > Network & internet, find DNS server assignment > Edit and restore Automatic (DHCP) when that is the network's expected configuration. Retest. Managed networks may require internal resolvers for company resources; ask IT before changing them.

For escalation, provide the affected domains, test time, resolver address, exact error, and whether another device works. If DNS succeeds but wired browsing still fails, use Ethernet websites-not-loading checks; do not repeatedly flush a cache that is already resolving correctly.

When hardware may be involved

When hardware is less likely, but still possible

DNS errors are usually not the first sign of failing hardware, but hardware can still be involved if the adapter keeps dropping, the router is unstable, or the whole connection is more broken than the error message suggests.

Professional help

When to seek professional help

Get help if several devices keep hitting the same DNS issue, if router reboots and cache flushes do not help, or if the problem returns so often that it is clearly part of a bigger network or ISP issue rather than a one-off Windows glitch.

Related fixes

Related network troubleshooting guides

Helpful guide Wi-Fi Connected But No Internet Use this if the DNS error is showing up over wireless and the bigger symptom is no internet. Open guide Helpful guide Ethernet Connected But No Internet Compare wired behavior to figure out whether the issue is only Wi-Fi or the whole network path. Open guide Helpful guide Repair Corrupted System Files in Windows Use this only if broader Windows networking damage seems likely after failed updates or crashes. Open guide

FAQ

What does DNS server not responding mean in Windows?

It usually means your laptop can still see the network, but it cannot translate website names into the addresses needed to reach them. That is why the internet can look half-alive but still fail in practice.

Can Wi-Fi be connected and still have a DNS problem?

Yes. DNS trouble is one of the most common reasons Wi-Fi looks connected while websites refuse to load.

Should I change DNS servers right away?

Not always. It is worth checking router restarts, DNS cache, and whether the problem affects multiple devices before you start swapping DNS settings.

Can the router cause a DNS server not responding error?

Yes. Routers often pass along DNS information, so a router or modem issue can show up as a DNS failure even when Windows itself is fine.

When is the ISP more likely to be the cause?

If several devices on the same network suddenly show the same DNS symptoms, the router, modem, or ISP is more likely than one Windows laptop.

When should I get professional help for DNS issues?

Get help if the issue affects multiple devices for a long time, keeps returning after router and adapter checks, or comes with wider network instability that points beyond simple DNS settings.