If Windows says you’re connected but names like `example.com` or a server hostname won’t open, the link is up and DNS is failing. The quickest fix is to prove IP connectivity works, check which DNS server Windows uses, and then correct the adapter, browser, VPN, hosts file, or upstream DNS path that’s breaking lookups. Flushing the cache can help when the bad answer is local, but it won’t fix the wrong server or a bad network profile.
Symptom
The usual pattern is straightforward: the network icon looks normal, websites still fail by name, and direct IP access may still work. That means the machine can send traffic, but name resolution is breaking somewhere between Windows, the adapter, and DNS.
A useful first split is this: if ping or another IP-based test works but nslookup returns no answer or the wrong server, you’re looking at a DNS problem rather than a dead connection. If several devices on the same network fail the same names, the fault is more likely in the router, ISP, or enterprise DNS than on the Windows box itself. If only one browser fails, check that browser’s secure DNS or proxy path before you touch Windows-wide settings.
Before you start
Use a Windows 10 or Windows 11 client, or an equivalent supported Windows desktop, and make sure you can open an elevated Command Prompt or PowerShell window. If this is a managed work device, stop before changing adapter settings, VPN software, or firewall policy you do not own.
Before you change anything, collect three things:
- the active adapter name
- the DNS server Windows is using
- whether name lookups fail on every app or just one browser
If you are on Wi-Fi, docking stations, VPNs, or multiple adapters, Windows may send DNS through a different interface than you expect. If you have to test a change, do it one step at a time so you can tell which layer fixed it or made it worse.
Fix the DNS path in order
- Prove that IP connectivity works while name resolution fails.
ping 1.1.1.1
nslookup example.comIf the IP ping works but nslookup fails or points to an unexpected server, the network is up and DNS is the problem. If both fail, you may have a broader connectivity issue, a captive portal, or a security tool blocking traffic before DNS even matters.
- See which DNS server Windows is actually using.
ipconfig /allLook at the active adapter, not just the one you remember using last. Check the listed DNS servers, the connection-specific DNS suffix, and whether the adapter is getting DNS from DHCP or from a static manual setting. If the wrong server is listed, the fix is in the adapter, VPN, or DHCP scope, not in the browser.
- Check whether this is only one app, one browser, one adapter, or the whole machine.
Try the same hostname in another browser and then with another network path if you have one, such as Ethernet instead of Wi-Fi or a disconnected VPN. If only one browser fails, browser secure DNS, proxy, or extension settings are a stronger suspect than Windows DNS itself. If only one adapter fails, focus on that adapter’s DNS servers, suffixes, and VPN profile. If every app on every adapter fails, look harder at the local cache, the hosts file, or upstream DNS.
- Inspect the adapter’s DNS settings and fix obvious mistakes.
Open the adapter’s IPv4 properties and confirm the DNS setup matches how the network is meant to work. A normal DHCP setup should receive DNS automatically from the router, VPN, or domain network. A static setup should point to known working DNS servers for that network, and the default gateway should match the local router or network path. If the adapter has stale, blank, or unrelated DNS entries, correct them there first. The exact server values depend on your network and should be checked against the current DHCP scope, router, or enterprise DNS policy rather than guessed.
- Flush the local DNS cache only when a cached answer may be the issue.
ipconfig /flushdnsUse this when the failure looks recent, one name is wrong, or you suspect Windows cached a stale record. It helps only if the bad answer is sitting in the local cache; it will not fix an unreachable DNS server, a wrong adapter setting, a browser-only DNS path, a hosts file override, or a VPN that is bypassing the local resolver.
- Check the hosts file for local overrides.
If one internal name resolves differently from what you expect, inspect C:\Windows\System32\drivers\etc\hosts for a manual entry. A single bad line there can override DNS for that name on the whole machine. If the entry was added for a temporary test, remove it and try the lookup again.
- Check browser-only DNS settings and VPN or security software.
If the browser fails but nslookup works, the browser may be using its own secure DNS settings instead of Windows DNS. If the problem started after a VPN or endpoint security change, that software may be pushing its own resolver, proxy, or filter driver. In one Windows VPN case, DNS resolution worked only under one specific configuration, and the client ignored the expected local DNS proxy when a single domain was set. That split behavior points to the VPN or client policy, not general Windows name resolution.
- Compare DHCP DNS to static DNS, then put the adapter back into the right mode.
If the network is meant to hand out DNS automatically, the adapter should get server addresses from DHCP. If the network requires static DNS, the adapter should show the approved servers and no leftover values from another network. A bad manual DNS entry can be enough to make a healthy link look broken. On some systems, a quick test is to switch temporarily to known working DNS servers on the active adapter, then switch back once you know whether the problem follows the adapter or the upstream server. If a temporary test fixes it, the next step is to correct the real DHCP, router, or enterprise DNS assignment instead of leaving the workaround in place.
- Decide whether the fault is upstream.
If multiple devices fail the same names, or if nslookup reaches the DNS server but the server cannot answer, the issue is probably upstream in the router, ISP, or enterprise DNS infrastructure. Microsoft’s DNS troubleshooting guidance also treats server reachability and root-hint path checks as part of DNS diagnosis, which is a good reminder that a local client cache is only one piece of the chain. If you are on a corporate network, pass the problem to the DNS or network team once you’ve shown that the Windows client can reach IP addresses but not resolve names.
Short fix matrix
| What you see | Likely cause | First place to check |
|---|---|---|
| IP works, names fail everywhere | DNS server, adapter DNS, or local client cache | nslookup, ipconfig /all, adapter settings |
| Only one browser fails | Browser secure DNS or proxy | Browser DNS settings, extensions, VPN |
| Only one adapter fails | Adapter profile or DNS suffix | That adapter’s IPv4/IPv6 DNS settings |
| Only one internal host fails | Hosts file, suffix, or stale record | hosts, DNS suffix, cache |
| Several devices fail the same names | Router, ISP, or enterprise DNS | Upstream DNS path and server health |
If you need a quick external check while testing, compare the client’s behavior against a known good public name and a known internal name. That tells you whether the break is general or limited to your internal DNS path.
Verify it worked
Run the same lookup again after each change and make sure the server answer is now sensible.
ipconfig /flushdns
nslookup example.comYou want nslookup to return a valid address from the DNS server you expect, and you want the browser or app to open the hostname without falling back to an IP address. If name lookups now work on one adapter but not another, the problem is still tied to the failing adapter or profile. If lookups still fail everywhere after you’ve confirmed the DNS server and hosts file are correct, stop changing local settings and check the router, VPN concentrator, ISP, or enterprise DNS server next.
Conclusion
If you can prove that IP works but names do not, you’ve already narrowed the problem to DNS instead of the whole network. From there, fix the active adapter’s DNS settings, browser or VPN overrides, or the upstream DNS server that Windows is querying.
Frequently Asked Questions
Why does Windows say I’m connected but websites won’t open by name?
Windows can show an active link even when DNS is broken. In that case, the machine can move traffic, but it cannot translate hostnames into IP addresses, so names fail even though the connection looks fine.
When should I use `ipconfig /flushdns`?
Use it when you suspect Windows cached a stale or poisoned record. It helps only if the bad answer is sitting in the local cache; it will not fix the wrong DNS server, a VPN override, a bad hosts file entry, or browser-only DNS settings.
What does `nslookup` tell me that a browser error doesn’t?
`nslookup` shows which DNS server Windows queried and whether that server returned an address. A browser error can hide that detail, so `nslookup` is better for telling client problems from server or path problems.
Sources
- Solved: DNS server not responding Windows 10 | Experts Exchange (experts-exchange.com)
- DNS resolution is not working on Windows after upgrading to 0.59.0 · Issue #4567 · netbirdio/netbird · GitHub (github.com)
- Troubleshooting DNS Servers | Microsoft Learn (learn.microsoft.com)