remember this one?
been busy the entire day to find out bullseye (fresh install) reconfigures unbound
the solution is the same, comment out the unbound entry in /etc/resolvconf.conf, however, if resolvconf managed to run with the entry active, it creates a file /etc/unbound/unbound.conf.d/resolvconf_resolvers.conf. You need to delete that file and restart unbound to resume normal behaviour.
The file created on my system contained only IPv6 info (IP address masked):
# Generated by resolvconf
forward-zone:
name: "localdomain"
forward-addr: xxxx:yyyy:zzzz:6902:e7ba:9aaa:fe18:c808
forward-zone:
name: "."
forward-addr: xxxx:yyyy:zzzz:6902:e7ba:9aaa:fe18:c808
This is the IPv6 address of my pi
The result is that all queries received by unbound are forwarded to pihole-FTL, most of the queries (all IPv6 queries) in the query log appeared to be comming from pi.hole (normally, that count is close to zero).
It also increases the number of status 14 (Already forwarded, not forwarding again) dramatically.
my scripts deleted the file (/var/cache/unbound/resolvconf_resolvers.conf), used in buster (had zero impact), but the file has been relocated in bullseye, with the very unpleasant result (unbound forwarding to pihole-FTL).
moderators / developers: you might want to add this test to pihole -d, check for the existance of the file, users might (will?) be impacted...
DL6ER: is there a way to get this warning (and others) in the tools / pihole diagnosis (message table) using bash?