I have a doubt, that unbound_manager does not save the cache properly.
The larger the cache gets, the lesser is saved when "rs".
Code:
11:51:43 Checking 'unbound.conf' etc. for valid Syntax.....
11:51:43 Saving unbound cache to '/opt/share/unbound/configs/cache.txt' msg.cache=5110/4640 rrset.cache=8250/7570
11:51:43 Requesting unbound (S61unbound) restart.....
Shutting down unbound... done.
Starting unbound... done.
11:51:45 Checking status, please wait.....
11:51:47 Restoring unbound cache from '/opt/share/unbound/configs/cache.txt' (2021-11-28 11:51:43) msg.cache=0/4640 rrset.cache=0/7570
11:51:47 unbound OK
NOTE: As stated in the
unbound-contro
l manual
I have stated in previous posts, that to eliminate any possibility of stale/invalid cache entries being restored, ideally the 'debugging' Cache load feature should really be removed from
unbound_manager
in favour of a custom cache seeding script that is invoked when starting
unbound
but currently for most users it works and provides a benefit.
However, your doubt's valid, the reported
restored Cache metrics is
technically correct but clearly
misleading, consequently I have uploaded
unbound_manager
Beta
v3.23bC to the Github dev branch to correct the report - i.e. the
restored cache metric is not actually 0.
To Upgrade/test use
Code:
e = Exit Script [?]
A:Option ==> uf dev