regards,
Bruno Ortega Blanes
> From: Yorgos Thessalonikefs
> To: unbound-users@lists.nlnetlabs.nl
> Subject: Re: Redis cache issues
> Message-ID: <920c43be-cd3c-4801-a197-27abb51a9...@nlnetlabs.nl>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hi Bruno,
&
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
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,
