tomsk
Very Senior Member
That is due to all your responses being cached properly and being used properly(hopefully). the question is, do you have any stale cache getting used?
Code:total.num.expired=9226
looking at the unbound.conf i would say yes but its limited to an hour after the ttl expires.
Code:
serve-expired: yes
serve-expired-ttl: 3600
serve-expired: <yes or no>
If enabled, unbound attempts to serve old responses from cache
with a TTL of serve-expired-reply-ttl in the response without
waiting for the actual resolution to finish. The actual resolu-
tion answer ends up in the cache later on. Default is "no".
serve-expired-ttl: <seconds>
Limit serving of expired responses to configured seconds after
expiration. 0 disables the limit. This option only applies when
serve-expired is enabled. A suggested value per draft-ietf-
dnsop-serve-stale-10 is between 86400 (1 day) and 259200 (3
days). The default is 0.
Not sure if the prefetch number is indicative of the stale cache hits?.... seems to fit... supplied from cache but recursive lookup performed
Code:
total.num.prefetch=13901
threadX.num.prefetch
number of cache prefetches performed. This number is included
in cachehits, as the original query had the unprefetched answer
from cache, and resulted in recursive processing, taking a slot
in the requestlist. Not part of the recursivereplies (or the
histogram thereof) or cachemiss, as a cache response was sent.
Last edited: