Troubleshooting

Troubleshoot a DNS lookup timeout

Use a layered diagnostic path to separate client configuration, local reachability, resolver health and upstream name resolution.

Local reachabilityLocal reachabilityQuery times outQuery times outresolver ↔ authoritativeClient192.0.2.25Client — 192.0.2.25Default gateway192.0.2.1Default gateway — 192.0.2.1Recursive resolver192.0.2.53Recursive resolver — 192.0.2.53Authoritative DNS203.0.113.53Authoritative DNS — 203.0.113.53
Legend

Current step

Confirm the client configuration

Check the assigned resolver address, search suffix and whether the client is using the expected network interface.

Choose the next test

The client can reach its default gateway but DNS queries time out. What should you test next before changing configuration?

Reveal diagnosis

Test reachability and service response from the client to the configured resolver, then inspect resolver health and upstream resolution separately.

Test one boundary at a time and record the result. A timeout is a symptom, not proof of a specific failure; compare name lookups with direct IP connectivity and inspect the resolver path.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Tags

  • troubleshooting
  • dns
  • timeout
  • diagnosis
  • layered tests

Lessons using this diagram