Hi Andreas, Yes that is what it does. Unbound also attempts to refresh and fetch the new correct value for the record, every time it is asked. That should bring the record back to the correct value. Once it is available to be fetched.
That makes the 0 value possible as a default, it is used until a better value becomes available. Best regards, Wouter On 7/11/19 5:04 PM, A. Schulze via Unbound-users wrote: > > Hello, > > I run an unbound instance with "serve-expired: yes" > Today I notices a record I deleted hours ago is still served by unbound. > Domains SOA negative ttl is 1h, too. > The I found "serve-expired-ttl" with a default value of 0 meaning no > expiration. > > So will unbound happily serve a deleted record for a very very long time > unless unbound has to kick it from it's cache for some reasons that are not > really visible to me? > > In that case the default "0 / no expire" is questionable. > > Andreas >
signature.asc
Description: OpenPGP digital signature
