pfSense

Switched. Thank you!

Why did this change in 2.8.0? I never had errors about memory before the update..

Jim Pingle wrote in #note-1:

Priority changed from Normal to Very Low

Should this be a HIGH protity. If I was getting crash log error message like this I'd want an update pushed out to explain WHY its crashing. Maybe update kea2unbound to say "Hey if your getting this error, and using PFblockerNG try changing your unbound mode from unbound to unbound python mode"
Or maybe update PFblockerNG to default to unbound python mode, or simular to how you told us the old DHCP was being depraticated and to switch to kea. Maybe say "Hey you should update this"...

kea2unbound is new in CE 2.8.0. Kea did not have DNS registration functionality before.

You can easily switch pfBlockerNG DNSBL modes to work around it, it does not necessarily require a fix in kea2unbound, I left this open in case we can find a way to make kea2unbound more tolerant of that situation in the future.

If the pfBlockerNG developer wants to detect that and change the pfBlockerNG behavior based on the DHCP daemon, that's up to them, but that's not a high priority base system issue.

I hit this same issue and figured it out thanks to this issue being reported, so thanks. I do think it would be good if kea2unbound itself would notice that pfBlockerNG is using the incompatible unbound mode without python. I spent a few hours figuring this out and it would have saved me a bit of time if there were an actionable error message. So, I broadly agree with Troy's sentiment.