Hi Bruno,
TTL 0 is explicitly returned for expired items in the external cache.
This means that 'serve-expired: yes' needs to be configured, otherwise
those items are not used.
Unbound will refuse to start if the connection to the external cache
cannot be established.
However, during operation if the connection drops, Unbound will silently
ignore lookup and store operations to the external cache until the
connection is up again.
I am not sure which version you are using, but what I described is true
for the latest version at least.
Best regards,
-- Yorgos
On 25/03/2024 19:53, Bruno Blanes via Unbound-users wrote:
Hello again,
Why is it that CacheDB returns TTL 0 for items that originate from the
external cache? Why not use the redis timeout when setting
redis-expire-records?
Also, is it possible to make Unbound not stop in case the cache goes
off-line? Could it fall back to resolving queries by default and
periodically ping the db to see if it’s back online?
