Public bug reported:
Hi,
I'm running unbound as an additional nameserver for tests with
interface: 127.0.0.1@5003
interface: 10.1.2.3@5003
so unbound-checkconf -o interface prints
127.0.0.1@5003
10.1.2.3@5003
The result is that
unbound-resolvconf.service
fails, since unbound-helper calls
resolvconf -a lo.unbound
with an empty input, which fails with "No DNS servers specified,
refusing operation." and thus makes the systemd unit fail.
As far as I can see it is a bug in line 40 of unbound-helper which is
[ -z "$default" ] ||
but probably should be
[ -z "$default" ] &&
or not call resolvconf at all if there is no nameserver on a port 53.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: unbound 1.19.2-1ubuntu3.3
ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
Uname: Linux 6.8.0-51-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: lxd
CloudName: lxd
CloudPlatform: lxd
CloudSerial: 20241119
CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
Date: Tue Dec 31 20:48:10 2024
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: unbound
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: unbound (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cloud-image noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092779
Title:
unbound-helper fails to properly detect nameservers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/2092779/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
