Resolver cache restored
-
PFSense: 23.01-RELEASE (amd64)
built on Fri Feb 10 20:06:33 UTC 2023pfBlockerNG-devel: 3.2.0_3
I have been monitoring unbound stats fairly closely to try and optimise the DNS cache. PFSense is in resolver mode as per default.
I don't register any DHCP leases in Unbound and only setup pfBlockerNG to perform an update once a day at 04:15. This is the only time I see a restart of unbound to avoid loss of cache.
The PFBlocker update process does a cache restore as expected.
After the restore I observe my cache size is reduced. There is a slight increase in cache hit rate but I am starting this off slow so don't have the load just yet.
Just curious whether this is normal behavior and the restore is working as it should? i.e. there is some kind of cleanup / reorganisation done during a restore like a 'reorg of a database'?
Monitoring unbound using "/usr/local/sbin/unbound-control -c /var/unbound/unbound.conf $* | grep -vE 'thread[0-9]+'" through Telegraf into Grafana as per
https://github.com/VictorRobellini/pfSense-Dashboard
