After three or four days of banging my head, I stumbled across a thread that already talked about this issue: WARNING: Raspbian October 2021 release bullseye + unbound, and the devs know about it. But seems there is a reluctance to put a warning or other user notification about it.
It appears that when I did my apt update/upgrade, it borked up the resolvconf.conf file and created another file that together prevent unbound from working properly. So yes, the issue still exists.
My Solution(from above thread):
- stop
unbound-resolvconf.service - Edit
/etc/resolvconf.conf
#resolv_conf=/etc/resolv.conf
#unbound_conf=unbound_conf=/etc/unbound/unbound.conf.d/resolvconf_resolvers.conf - delete file:
/etc/unbound/unbound.conf.d/resolvconf_resolvers.conf - reboot
After reading that thread several more times, and just for good measure, I also executed the command to replace openresolv with standard resolvconf as well. This should prevent future unintended restarts of unbound.
dpkg-query -s 'openresolv' &> /dev/null && apt -y install resolvconf