Why does a DNS query get no answer?
A DNS query with no response means the question never reached the resolver or the answer never came back: the resolver is down or unreachable, a firewall blocks port 53, or the device is using a DNS server that isn't there. Apps wait and retry, which looks like the whole internet is slow or broken.
What it looks like in the packets
- DNS queries to port 53 with no matching response (same transaction ID, address, and port).
- Retries after 1–5 seconds, sometimes to a second DNS server.
- No connections start until a name resolves.
Common causes
- The configured DNS server is down or unreachable.
- A firewall or VPN blocks UDP and TCP port 53.
- The device has a stale DNS server from an old network.
- The capture ends before a late answer.
What to check
- Check which DNS server the queries go to, and whether that address answers anything.
- Query another resolver directly to rule out the name.
- Check firewall rules for port 53.
Wireshark display filters
dns.flags.response == 0 && !dns.response_in
How Blame Finder flags it
Low; Informational when the capture has no DNS answers at all or only one direction. Upload a capture and the finding links straight to the packets behind it, with the most likely culprit at the top.