DNS server not responding
Windows couldn't get an answer from its DNS server
Seen in Windows Network Diagnostics, macOS and Windows troubleshooters
Windows reached the network but its DNS server did not answer lookups, so names do not resolve.
Common causes
- The router's DNS forwarder or the ISP's resolver is down or hung.
- Manual DNS settings point to a server that no longer works, or a VPN left them behind.
- A firewall or security product blocks DNS traffic.
How to fix it
- Restart the router, then run `ipconfig /flushdns` and `ipconfig /renew`.
- Set a known-good resolver such as 1.1.1.1 or 8.8.8.8 on the adapter to test.
- Disconnect VPNs and temporarily disable third-party security software to find the blocker.
Got a different message? Paste it into the error explainer.
Related errors
- DNS_PROBE_FINISHED_NXDOMAIN · The domain name doesn't exist
- SERVFAIL · The DNS server failed to answer
- REFUSED · The DNS server refused the query
- ERR_NAME_NOT_RESOLVED · The browser couldn't resolve the hostname
- DNS_PROBE_FINISHED_BAD_CONFIG · The configured DNS server is not working
- ** server can't find example.com: NXDOMAIN · nslookup says the name doesn't exist
- *** UnKnown can't find · nslookup couldn't name the DNS server, then the lookup failed
- Non-authoritative answer: · The answer came from a resolver cache, which is normal
- ;; connection timed out; no servers could be reached · No DNS server answered the query
- status: NOERROR, ANSWER: 0 · The name exists but has no record of that type
- FORMERR · The DNS server could not parse the query
- NOTIMP · The DNS server does not support that kind of query