Hi Bruno,
Current master branch has an unreleased fix to ignore Redis if not there
during startup/reload.
Previously it was not ignored during these events.
Unbound has connection and command timeouts for Redis.
The default is 100ms for both and I believe each query pays the timeout
penalty when trying to load and store values.
Maybe we need a backoff timer when Unbound can't connect?
Best regards,
-- Yorgos
On 31/01/2025 14:44, Bruno Blanes via Unbound-users wrote:
Good morning folks,
I noticed that Unbound will not start if Redis cache is configured but
unreachable, can anyone elaborate on the design choice behind this?
Also, I’ve noticed that when the cache connection is refused, Unbound
works just fine querying the root servers and returning the answer,
however if the connection timeout, aka Redis server shutdown, all
queries timeout rendering my DNS useless.
Is this a config issue on my side or also by design?
Best regards,
Bruno Ortega Blanes
