DNS GLOSSARY
DNS timeout
A DNS timeout means a resolver did not receive a reply before its waiting period ended. It describes a missing response, not a DNS response code.
What a DNS timeout means
A DNS client or recursive resolver sent a query but did not receive a usable reply before its configured wait period expired. Resolvers may retry the query or try another name server, so the time shown by an application can include several attempts.
A timeout does not tell you why the reply was missing, and it does not prove that the domain has no DNS records. It is different from SERVFAIL, NXDOMAIN, or NOERROR, which are codes in DNS responses.
Illustrative example
Question: example.com. IN A Wait period: 2 seconds Observation: no DNS reply arrived before the wait ended
The two-second period is only an example. Clients and resolvers use different timeout and retry settings.
How to investigate
- Retry the same name and record type once, and note the resolver, network, and exact error shown.
- Compare results from another trusted resolver or network. If only one resolver times out, check its availability and path to the authoritative name servers.
- Check packet loss, routing, and firewall rules for DNS over both UDP and TCP on port 53. A timeout alone cannot distinguish among these causes.
- If you operate the DNS service, review resolver and authoritative-server logs around the query time.
Use the DNS Lookup page to compare the response for a specific name and record type. A returned response code is different from receiving no reply.
References
RFC 9520 — Negative Caching of DNS Resolution Failures · RFC 1035 — Domain Names: Implementation and Specification
Related pages
NOERROR · SERVFAIL · NXDOMAIN · DNS Lookup