The unbound guide (unbound - Pi-hole documentation) talks about disabling resolvconf.conf entry for unbound for debian bullseye and later. I have bookworm. The command "systemctl is-active unbound-resolvconf.service" returns "inactive". However, the file "/etc/resolvconf.conf" doesn't exist, and /etc/resolv.conf contains "nameserver 192.168.1.1".
I started unbound's logging, and nothing is being logged.
Thats a good sign.
The whole purpose of disabling that unbound-resolvconf.service is to prevent it from wrongfully populating the /etc/resolv.conf file with the localhost IP 127.0.0.1.
Yours is populated with your router IP 192.168.1.1 which is fine.
How did you start Unbound logging?
Why?
And what do you expect find?
It can be a bit cryptic to decipher 
Some pointers about logging (check the verbosity bit):
Thanks for the reply. I just discovered an error in the configuration file; I can now see that unbound is working (which is why I started the logging).
FWIW, openresolv is not installed on my system, maybe the problem was fixed in Bookworm.
$ sudo unbound-checkconf
unbound-checkconf: no errors in /etc/unbound/unbound.conf
$ hostnamectl
[..]
Operating System: Debian GNU/Linux 12 (bookworm)
$ apt policy openresolv
openresolv:
Installed: (none)
Candidate: 3.12.0-3
EDIT: But below one is:
$ dpkg -L unbound
[..]
/lib/systemd/system/unbound-resolvconf.service
$ systemctl cat unbound-resolvconf.service
# /lib/systemd/system/unbound-resolvconf.service
# This is a helper unit to register local unbound resolver daemon in
# resolv.conf.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.