DNS server not responding: find the failing step
Separate a DNS problem from a connection failure, compare devices and resolvers, and keep a path back to your original settings.
Website: https://zenshield.com/help/dns-server-not-responding
Canonical URL: https://zenshield.com/help/dns-server-not-responding
Page reviewed: 2026-09-12
A DNS error means a name lookup did not complete as expected. The failure can be in the device, resolver, network or domain itself. Start by finding its scope before replacing DNS settings.
Narrow it down
Try two unrelated websites. Then test the failing website from another device on the same network, if you have one available.
| Observation | Investigate next |
|---|---|
| Only one domain fails on several devices | The domain’s DNS or website |
| Many domains fail on one device | That device’s browser, DNS and network settings |
| Many domains fail on every device | Router, internet service or shared resolver |
| Failure happens only after VPN connection | VPN DNS settings, browser Secure DNS and routing |
A website availability check answers a different question: whether the site responds to our server. Use the website checker for that clue, without treating it as proof of a worldwide outage.
Compare a public DNS answer
Enter the failing domain in DNS lookup. An answer there means Google Public DNS supplied records. It does not show that your own resolver is healthy. NXDOMAIN means that resolver considers the name nonexistent; check spelling before changing your device.
If Windows may have an old answer, flush its DNS cache once and retest. If you deliberately choose a different resolver, record the original settings first. Use the resolver’s published addresses and instructions.
Avoid a permanent mystery configuration
Changing DNS can affect filtering, internal company names and family controls. Make changes only on a device or network you may administer. Restore the previous setting if the experiment does not help.
When asking for support, include the domain, error text, time and whether other devices worked. Do not send a complete browsing history or private internal hostnames in a public post.