When a domain stops resolving, the failure may not be accidental. Some networks block or rewrite DNS responses on purpose.
Step-by-step solutions
- Test the same domain with your current resolver and with a public resolver.
- Compare the result on another device or mobile network.
- Look for timeouts, captive portal redirects, or block pages.
- Check router parental controls, firewall rules, and browser secure DNS settings.
Useful commands
Windows
nslookup example.com 1.1.1.1
nslookup example.com 8.8.8.8
macOS
dig example.com @1.1.1.1
dig example.com @8.8.8.8
Linux
dig example.com @9.9.9.9
resolvectl query example.com
If the problem looks like tampering rather than policy, read what DNS spoofing is. If the failure is broader and not domain-specific, continue with how to fix DNS server problems.

