Running Pi-hole on Bullseye with unbound - resolvconf file appears after reboot?

General Customizing Pi-hole
1

I run Unbound on my Pi-hole (Pi-hole [v5.8.1], FTL [v5.13], Web Interface [v5.10.1]) and using it successfully in my private network for all DNS-requests - Pi-hole is configured to use Unbound as Upstream-Server for IPv4 and IPv6.

Forgive me, if I'm asking dumb questions, but regarding

I recently updated all my Pis to bullseye and also ran into the problems described in that thread.
I successfully deactivated (propably not?) openresolv as described including deleting the /etc/unbound/unbound.conf.d/resolvconf_resolvers.conf file.

But - and that's my problem here - after a reboot the file still shows up magically... How can I avoid having the file generated on every reboot (unfortunately we had some electricty dropout and after rebooting, the Internet "was gone").

2
  1. Edit file /etc/resolvconf.conf and comment out the last line which should read:

unbound_conf=/etc/unbound/unbound.conf.d/resolvconf_resolvers.conf

  1. Delete the unwanted unbound configuration file:

sudo rm /etc/unbound/unbound.conf.d/resolvconf_resolvers.conf

  1. Restart unbound:

sudo service unbound restart

3 Likes
3

Wow! THAT was quick! Thank you!

2 Likes