I can reproduce the issue inside a Noble LXD container, by installing
'unbound' and starting 'unbound-resolvconf.service':
$ lxc launch ubuntu-daily:noble test
$ lxc shell test
# apt update && apt install unbound
# cat >> /etc/unbound/unbound.conf<< EOF
server:
interface: 127.0.0.1@5003
interface: 10.1.2.3@5003
EOF
# systemctl start unbound-resolvconf.service
# systemctl status unbound-resolvconf.service
× unbound-resolvconf.service - Unbound asyncronous resolvconf update helper
Loaded: loaded (/usr/lib/systemd/system/unbound-resolvconf.service;
enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2025-05-21 10:30:24 UTC; 1s
ago
Duration: 27ms
Process: 1365 ExecStart=/usr/libexec/unbound-helper resolvconf_start
(code=exited, status=1/FAILURE)
Main PID: 1365 (code=exited, status=1/FAILURE)
CPU: 18ms
# journalctl -b | grep resolvconf
May 21 10:35:57 unbound systemd[1]: Started unbound-resolvconf.service -
Unbound asyncronous resolvconf update helper.
May 21 10:35:57 unbound resolvconf[1439]: Dropped protocol specifier '.unbound'
from 'lo.unbound'. Using 'lo' (ifindex=1).
May 21 10:35:57 unbound resolvconf[1439]: No DNS servers specified, refusing
operation.
May 21 10:35:57 unbound systemd[1]: unbound-resolvconf.service: Main process
exited, code=exited, status=1/FAILURE
May 21 10:35:57 unbound systemd[1]: unbound-resolvconf.service: Failed with
result 'exit-code'.
# /usr/libexec/unbound-helper resolvconf_start
Dropped protocol specifier '.unbound' from 'lo.unbound'. Using 'lo' (ifindex=1).
No DNS servers specified, refusing operation.
In Debian bug https://bugs.debian.org/1019140 a relation with the split-
out systemd-resolved package is discussed:
"""
Since systemd was upgraded (251.3-1 -> 251.4-3) and systemd-resolved
became an own package which now provides /sbin/resolvconf, unit is no
longer being skipped and fails now
"""
Since version 1.17.1-2 (which we already have in Ubuntu 24.04), this
workaround should make things pass:
# echo RESOLVCONF=false > /etc/default/unbound
# systemctl start unbound-resolvconf.service
# systemctl status unbound-resolvconf.service
● unbound-resolvconf.service - Unbound asyncronous resolvconf update helper
Loaded: loaded (/usr/lib/systemd/system/unbound-resolvconf.service;
enabled; preset: enabled)
Active: active (exited) since Wed 2025-05-21 10:52:35 UTC; 4s ago
Process: 1607 ExecStart=/usr/libexec/unbound-helper resolvconf_start
(code=exited, status=0/SUCCESS)
Main PID: 1607 (code=exited, status=0/SUCCESS)
CPU: 6ms
May 21 10:52:35 unbound systemd[1]: Started unbound-resolvconf.service -
Unbound asyncronous resolvconf update helper.
Does that work for you? If so, we might consider having this
"RESOLVCONF=false" as a default, as Ubuntu comes pre-installed with
systemd-resolved. Or at least introduce corresponding documentation.
** Bug watch added: Debian Bug tracker #1019140
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019140
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unbound (Ubuntu)
Status: New => Triaged
** Changed in: unbound (Ubuntu)
Importance: Undecided => Medium
** Changed in: unbound (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2078599
Title:
unbound-resolvconf.service fails in LXD
Status in systemd package in Ubuntu:
New
Status in unbound package in Ubuntu:
Incomplete
Bug description:
Hi,
after upgrading an LXD guest machine from 22.04 to 24.04.1, systemctl
complains that units are failing:
● unbound-resolvconf.service loaded failed failed Unbound asyncronous
resolvconf update helper
Aug 31 19:19:25 install systemd[1]: Started unbound-resolvconf.service -
Unbound asyncronous resolvconf update helper.
Aug 31 19:19:25 install resolvconf[414]: Dropped protocol specifier
'.unbound' from 'lo.unbound'. Using 'lo' (ifindex=1).
Aug 31 19:19:25 install resolvconf[414]: No DNS servers specified, refusing
operation.
Aug 31 19:19:25 install systemd[1]: unbound-resolvconf.service: Main process
exited, code=exited, status=1/FAILURE
Aug 31 19:19:25 install systemd[1]: unbound-resolvconf.service: Failed with
result 'exit-code'.
# /usr/libexec/unbound-helper resolvconf_start
Dropped protocol specifier '.unbound' from 'lo.unbound'. Using 'lo'
(ifindex=1).
No DNS servers specified, refusing operation.
Looks like
https://groups.google.com/g/linux.debian.bugs.dist/c/rdluvEnL6BE
https://discuss.linuxcontainers.org/t/erratic-network-initialization-
in-lxc-container-with-unbound-dns/18680
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: unbound 1.19.2-1ubuntu3.1
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CloudBuildName: server
CloudSerial: 20221101.1
Date: Sun Sep 1 02:17:43 2024
SourcePackage: unbound
UpgradeStatus: Upgraded to noble on 2024-08-31 (0 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078599/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
