Stubby stops working after computer goes to sleep on OSX and other OS. Useless on a Laptop

[karz1]

Stubby stops working after computer goes to sleep on OSX and other Operating Systems.

Basically useless on a laptop

[teutat3s]

I can confirm that stubby takes 90-180 seconds to successfully resolve DNS queries after waking my laptop up from sleep.

This is on macOS 10.14.6 and with latest stubby 0.2.6. I'd love to help debug this and track down why this is happening.

[inudge]

I'd also like to investigate this but haven't been able to reproduce the problem so far. Perhaps you could provide more details about your configurations and use cases ?

[teutat3s]

Thank you for coming back to us.

I have used stubby in two different ways, and in both the described issue appears after waking the laptop up from sleep.

First setup was plain stubby, installed via brew, configured with default settings, default upstream resolvers, only change was enabling DNSSEC. Switched system DNS resolver to 127.0.0.1 - working great on a running system, only after sleep it took a long time for stubby to resolve correctly, SERVFAIL was the response in dig for the first two minutes.

Second setup that's now in use is unbound as caching resolver in front of stubby with the same configuration as above. Same issue appears, unbound cache doesn't seem to help after sleep...

Please tell me how I can help debugging this further.