If websites fail by name but a public IP address still responds, DNS is the likely layer. Confirm it before changing resolvers.
What DNS does
DNS translates names such as a website address into the numeric addresses computers use. When it fails, the connection can look healthy while browsers report that a server cannot be found.
How to confirm DNS is the problem
Ping a public IP address. If it replies but pinging a website name fails, name resolution is the likely failure. You can also use nslookup with a domain name; timeouts or server-failure responses point to the configured resolver.
- IP address reachable, names fail → DNS.
- Both fail → connectivity problem, not just DNS.
- Only one site fails → that site or its record, not your resolver.
Safe fixes, in order
Start with the least invasive actions and retest after each one.
- Restart the router and the PC.
- Clear the Windows resolver cache with ipconfig /flushdns.
- Try another resolver on the adapter, then remove it if it makes no difference.
- Disable VPN or filtering software briefly to see whether it intercepts DNS.
- Use a network reset only if the above does not help and the network stack looks damaged.
Router versus PC
If several devices have the same DNS trouble, the router or provider resolver is the common factor. Changing the DNS server on the router fixes it for every device, while changing it on the PC fixes only that PC.
A DNS error should be tested, not guessed from the browser message
A failed website lookup can come from the current DNS resolver, a local cache, a VPN or security product, a router issue, or the destination domain itself. First test more than one unrelated domain and check whether another device on the same network has the same problem. A single website failure is not enough evidence to replace DNS settings.
In PowerShell, use Resolve-DnsName for a domain and compare it with nslookup if needed. A timeout, SERVFAIL, NXDOMAIN, and a successful response are different outcomes: NXDOMAIN can mean that the queried name does not exist, while a timeout means the query did not receive a response in time. Confirm the domain spelling and query a known-good domain before drawing a conclusion.
Resolve-DnsName example.com
nslookup example.com
Test-NetConnection example.com -Port 443- If name lookup fails for multiple domains but general connectivity works, investigate DNS resolution and the configured resolver.
- If the DNS test succeeds but a browser still fails, check proxy/VPN settings, browser-specific errors, and the destination service.
- If several devices on the same network fail together, investigate router DNS settings or upstream service before changing one Windows PC.
- Change one variable at a time and record the original resolver settings so you can reverse the test.
Separate a resolver problem from a browser or connection problem
Use more than one unrelated domain when testing DNS. A domain-specific NXDOMAIN response can be legitimate, while a timeout means the resolver did not reply in time; neither outcome alone proves that every DNS request is broken. Compare the normal lookup with a known public resolver only when your network policy permits it.
A successful DNS lookup proves that a name was resolved, not that the resulting website is reachable or healthy. If lookup succeeds but the browser fails, test the HTTPS connection and review proxy, VPN, filtering, certificate, and browser-specific errors before changing resolver addresses.
| Result | What it means | Next check |
|---|---|---|
| Several unrelated names time out | Resolver reachability or network filtering may be involved | Compare another device and inspect VPN, router, and resolver settings |
| One domain returns NXDOMAIN | That queried name may not exist or may be mis-typed | Verify the spelling and test a known-good domain |
| DNS succeeds but HTTPS test fails | The fault may be route, firewall, proxy, destination service, or TLS-related | Review the connection error and test another trusted site |
| Only one PC has failures | Local cache, VPN, adapter, or endpoint software may be involved | Compare settings and test one change at a time |
Resolve-DnsName example.com
nslookup example.com
Test-NetConnection example.com -Port 443See the evidence behind this topic
These TWW research pieces examine the measurements, mechanisms, or testing questions related to this guide. Research pages distinguish measured results from general technical guidance.
- Windows Shows 100% Disk Usage but Very Low MB/s: What Is Actually Happening?100% active time is not the same thing as 100% storage bandwidth. The difference is the key to diagnosing many Windows disk complaints.
- Does More RAM Actually Make Windows Faster? What to Measure Before UpgradingRAM capacity is valuable when the workload needs it. The mistake is treating every slow PC as a memory-capacity problem.
Sources & further reading
Frequently asked questions
Is changing my DNS server safe?
Yes, it is reversible. Choose a resolver you trust, test the result, and set the adapter back to automatic if it does not help.
What does ipconfig /flushdns do?
It clears the local DNS cache so Windows asks a resolver again instead of reusing old answers. It does not change your settings.
Does a successful ping to an IP address prove DNS is broken?
No. It is one clue. Compare name-resolution results, more than one domain, other devices, and the browser or application error before identifying DNS as the failing layer.
We distinguish documented facts, measured results, and informed guidance. If a claim depends on a specific device, software version, game, or test method, that context should be stated rather than implied.
Meet the author·See our testing methodology·Read our editorial policy