unbound keeps stopping

[costanzo]

Recently started to notice the unbound service stopping. It seems to occur when pfBlockerNG-devel updates.

Background:
21.05-RELEASE (arm64)
built on Tue Jun 01 16:52:48 EDT 2021
FreeBSD 12.2-STABLE

pfBlockerNG-devel 3.0.0_16
Using Unbound Python Mode
Register DHCP leases in the DNS Resolver (Unchecked)

I would prefer not to use the service watchdog package to restart the service.

Any suggestions on how to pin point the cause and possible fix?

Thanks in advance.

[SteveITS]

https://forum.netgate.com/topic/158592/pfblockerng-devel-v3-0-0-no-longer-bound-by-unbound
"CAUTIONS:

The DNS Resolver (Unbound) DHCP Registration option is not compatible with DNSBL Python mode. The pfSense devs are aware and changes are required to be made to the dhcpleases binary to stop/start Unbound instead of sending a SIGHUP. The use of this option and the Unbound Python mode will cause an Unbound crash.
If DHCP Registration is enabled in Unbound Python mode, or DHCP Registration enabled after Unbound Python mode is enabled, Unbound Python mode will be downgraded to Unbound mode to prevent Unbound from crashing."

[Gertjan]

@steveits Python mode can only be selected and accepted if

@costanzo said in unbound keeps stopping:

Register DHCP leases in the DNS Resolver (Unchecked)

Btw : the dhcpleases program doesn't "restart" (stop and then starts again) unbound, it actually sends a SIGHUP to the unbound process.
Still, on the 21.0x version of pfSense, using the "arm" code, unbound can fail, this is already known. That's why the upcoming unbound version is downgraded.

All this is somewhat theory for me, as I'm not using an arm device, but an 'intel/amd' device, using pfSense 2.5.1 - pfsense version 1.13.1, which his rock solid for me.

[SteveITS]

@gertjan I skipped over "unchecked" apparently, sorry costanzo. Unbound was reverted to an earlier version in 21.05 but he has that already.