Build note
DNS failed while Wi-Fi was still connected
The laptop had Wi-Fi. DNS did not. That combination makes a network problem look like an application problem: the browser says a site cannot be found, but the wireless icon still says connected.
The resolver chain had two hops. Applications queried systemd-resolved at
127.0.0.53, and the local stub forwarded to Pi-hole at 10.0.0.42. The
stub requested EDNS0, an extension that lets DNS carry larger messages and
additional options. During the outage, systemd-resolved logged that it was
using a degraded UDP-only feature set for the Pi-hole server.
The fallback answered, but it did not filter
The router at 10.0.0.1 was configured as a fallback. It resolved ordinary
names, but it did not forward queries to Pi-hole. Testing an ad domain against
the router returned a real address, while Pi-hole returned the block response.
So the fallback preserved connectivity and dropped filtering.
The status output could be misleading. resolvectl showed the router as the
current DNS server, but that alone did not say whether every query used it or
whether the Pi-hole had also received requests. Fresh probe names and the
Pi-hole query log gave a direct check: all ten probes appeared in Pi-hole.
Why the application error was the wrong clue
The user-facing error was ERR_NAME_NOT_RESOLVED. That does not identify which
hop failed. The request might not have reached systemd-resolved; the local
stub might have failed to reach Pi-hole; Pi-hole might have refused it because
of the rate limit; or the router might have answered without filtering.
The checks were deliberately small:
- Ask
resolvectlwhich servers are configured for the active connection. - Resolve a fresh name through the system resolver.
- Check whether that exact name appears in Pi-hole’s query log.
- Compare a blocked domain through Pi-hole and through the router.
That separated “DNS is completely down” from “DNS works through an unfiltered fallback”. The rate limit had already been raised after the earlier query storm, so the later checks also verified the fallback behavior rather than assuming the same failure had returned.
The rule that would have prevented the next week
When Wi-Fi is connected but names fail, test each hop in order. A fallback resolver can make the browser work while quietly bypassing the filter. Check both the answer and the log that says which server handled the query.
How this was made
- Written by: Rupesh, from
resolvectl, DNS probe lookups and Pi-hole query logs, with AI drafting and editing. - AI-assisted sections: structure and copy editing.