Hi, it appears this bug never made it into my mailbox. Sorry for having missed it.
On Wed, Jun 12, 2024 at 06:45:01PM +0200, Eduard Bloch wrote: > every couple of days I get the same problem. I suspend the system for > some hours, and when I come back, the DNS resolution fails. I.e. doing a > ping on a hostname returns "Not found". ping is not super useful for debugging here. Could you try dig instead? > The system recovers from this condition after some time, sometimes > after a few seconds but sometimes not even after a minute (that is when > I restart the pdns-recursor service manually and everything suddenly > works like nothing has happened). > > NOTE: I have a vague feeling that the down-state of the NIC right after > suspend might be a contributor here. Sometimes it takes almost 5 second > to recover and set the IP address. > > Checking the journalctl (after the resuming timestamp), it reveals only: [..] I think you'll need to enable debug/trace logging to see something useful. And yeah, if the NIC is down, I expect sending packets will fail and you'll end up with negative cache entries. But dig will tell us more. Also it'd be good if you could talk directly to upstream, either on IRC or in a github discussion. They'll have more ideas on how to debug this. Thanks, Chris
