The DNS server that was asked never answered. When it is the domain’s own nameserver, the domain’s DNS is down or blocked; when it is your resolver, the problem is your network. dig and nslookup name the server they tried, which tells you which.
;; connection timed out; no servers could be reached
How 5 other clients word the same error
dig (BIND 9.18 and later)
;; communications error to 192.0.2.1#53: timed out ;; no servers could be reached
Windows nslookup
DNS request timed out.
timeout was 2 seconds.
*** Request to dns.example timed-out
curl
curl: (28) Resolving timed out after 5000 milliseconds
Node.js
Error: queryA ETIMEOUT example.com
systemd-resolved
resolve call failed: All attempts to contact name servers or networks failed
| Error | connection timed out; no servers could be reached |
| Usually fixed by | Either side |
| Resolvers give up after | A few seconds per server, then try the next |
| DNS needs | UDP and TCP port 53 open (RFC 9210) |
Check the domain’s nameservers
Enter the domain: we ask each of its nameservers in turn and show which ones answer.
What it means
A resolver waits a few seconds for each nameserver, retries, and moves on. When none answers, dig reports that no servers could be reached; a public resolver answering for you returns SERVFAIL instead, sometimes with the extended error “No Reachable Authority”.
Why it happens
- The domain’s nameservers are down, or their addresses at the registrar are wrong.
- A firewall dropping DNS on port 53 — or allowing UDP but not TCP, which large answers need.
- Your own resolver or network is down, when dig was asking the default server.
How to fix it
- Note which server the error names. The domain’s nameserver means the domain’s DNS; your resolver means your network.
- Check each of the domain’s nameservers with the check above.
- On the nameservers’ side, open UDP and TCP port 53 — DNS Flag Day 2020 made TCP support a requirement.
- On your side, try another resolver: dig example.com @1.1.1.1.
See it for yourself
dig example.com NS +short
dig example.com @ns1.example-dns.net +norecurse
dig example.com @ns1.example-dns.net +norecurse +tcp
A server that answers over UDP but not TCP will fail for large answers — DNSSEC-signed ones especially.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- BIND 9 source: dig/dighost.c — gitlab.isc.org
- RFC 9210 — rfc-editor.org
- DNS Flag Day 2020 — dnsflagday.net
- nslookup — learn.microsoft.com