I'm running unbound on Ubuntu 22.04.4 LTS and am getting this message when I start unbound. I've posted this issue in the Ubuntu forum, but have had no reply.
The service is up
1. After this happens, is /etc/resolv.conf a symlink or a real file?
2. In either case, what is the contents?
Copying to list, hopefully dropping all significant identifiable bits.
Just to clarify, the error I get is in syslog
resolv.conf is a link
/etc/resolv.conf -> /run/systemd/resolve/resolv.conf
That looks like you run systemd-resolved too.
What port is unbound configured to listen on? Is it the same port as
resolved (53 if you haven't changed config)? Is localhost included in
the addresses unbound listens to (again, it is by default)?
I think these 2 services are not compatible with each other in their
default config. Probably the simplest way to deal with it is to
disable systemd-resolved completely (you can do that with systemctl).
After that, make a static /etc/resolv.conf (not a symlink to anything)
which can be empty I think, or only contain search directives. And
restart the system. Now resolvconf should notice unbound is installed
and replace resolv.conf with one including a "nameserver 127.0.0.1"
line.
Alternatively, get rid of resolvconf too, by uninstalling it, and just
have a hand edited resolv.conf including a "nameserver 127.0.0.1"
line. This will only work if either unbound is configured as a full
recursive resolver (i.e. no forwarding) or the upstream server(s) it
forwards too are constant (so no wifi hopping and such).
Hth.
This is normal and a do-nothing warning.
In debian (and ubuntu), unbound service startup triggers startup of
unbound-resolvconf service too, - this is to tell resolvconf, if it
is present, about unbound presence.
The condition which you're seeing is in unbound-resolvconf.service:
ConditionFileIsExecutable=/sbin/resolvconf
so the service does nothing if there's no /sbin/resolvconf on your
system. And systemd is logging this message. Which is, as I
mentioned earlier, absolutely normal.
Unbound itself works as configured.
This is how the packaging is done in debian. And while I'm the
maintainer of unbound package in debian, I don't know why it's
done this way, - it was before my time.
Thanks,
/mjt