pfSense

This one is perhaps complicated to fix.

Currently if a unbound-control reload is issued then unbound will shutdown because of unable to read the unbound.conf file. pfSense developers I expect are already aware of this because the reload function is never used in pfSense code. However pfblockerng tries to use it but is broken because of the bug.

The correct way to start unbound is to use the configuration file at /usr/local/etc/unbound/unbound.conf and unbound itself will do whats needed to have the files it needs in the chroot location of /var/unbound.

For this to be changed, the scripts that generate the configuration would need the path changing as well as the scripts that start unbound.