unbound stops responding when connection to upstream breaks
unbound-users at chrissnell.com
Wed Feb 9 14:04:59 UTC 2022
I'm experiencing issues with unbound's connection to my upstream recursive resolver. Both my local caching forwarder and the upstream recursive resolver are running unbound. The problem happens every time the connection between the local server and upstream fails and when this happens, the local's connection to upstream will not reconnect. The connection might break due to a variety of things:
- wifi on the laptop changing APs
- connecting to a VPN
- rebooting the upstream recursive server
Whenever one of these conditions happen, queries to the local forwarder will fail and continue to do so until the local forwarder is restarted. Once it's restarted, everything works fine again. This feels like some kind of issue with TLS or a persistent connection.
Is there any way to force unbound to be a little more aggressive in reconnecting when something fails with networking?
Here's my local forwarder's unbound.conf:
And here is my upstream recursive resolver's:
access-control: 0.0.0.0/0 allow
interface: 0.0.0.0 at 443
ssl-service-key: "/etc/letsencrypt/live/<REDACTED>/privkey.pem <http://silcox.island.nu/privkey.pem>"
ssl-service-pem: "/etc/letsencrypt/live/<REDACTED>/fullchain.pem <http://silcox.island.nu/fullchain.pem>"
Any ideas? Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Unbound-users