not a najor problem but more of an anoying one .this is on a clean os install on my pi 4
my pihole is setup as a recursive dns works great till next reboot now what happens is
this file gets created @ unbound config folder resolvconf_resolvers.conf
has a forwarding address in it tha brakes the recursive dns deleting the file and restarting unbound solves the problem till i reboot and that file gets created again.
resolvconf is disabled not sure what is creating that specific file
I followed the steps to disable the unbound resolvconf service and then manually populated /etc/resolv.conf with my Pi's desired external nameservers, then tested it stayed like this across reboots, which it does.
I've not touched the native OS resolvconf – should I be similarly doing the steps in this solution to ensure no surprises down the line?
I only ask because it's not mentioned on the Pi-hole Unbound installation page in the section which talks about optionally turning off Unbound's own resolvconf service.
You are in a maze of twisty little DNS resolvers, all alike.