Package: bind9
Version: 1:9.20.4-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Sometime in the past an upgrade to bind9 stopped calling resolvconf on
startup/shutdown, leaving the resolver as it was set when dhclient/ifupdown
called resolvconf.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Downgraded to an old version of bind9 which worked:
Performing actions...
dpkg: warning: downgrading bind9 from 1:9.20.4-2 to 1:9.18.28-1~deb12u2
(Reading database ... 716202 files and directories currently installed.)
Preparing to unpack .../bind9_1%3a9.18.28-1~deb12u2_amd64.deb ...
Unpacking bind9 (1:9.18.28-1~deb12u2) over (1:9.20.4-2) ...
dpkg: warning: downgrading bind9-utils from 1:9.20.4-2 to 1:9.18.28-1~deb12u2
Preparing to unpack .../bind9-utils_1%3a9.18.28-1~deb12u2_amd64.deb ...
Unpacking bind9-utils (1:9.18.28-1~deb12u2) over (1:9.20.4-2) ...
dpkg: warning: downgrading bind9-host from 1:9.20.4-2 to 1:9.18.28-1~deb12u2
Preparing to unpack .../bind9-host_1%3a9.18.28-1~deb12u2_amd64.deb ...
Unpacking bind9-host (1:9.18.28-1~deb12u2) over (1:9.20.4-2) ...
dpkg: warning: downgrading bind9-dnsutils from 1:9.20.4-2 to 1:9.18.28-1~deb12u2
Preparing to unpack .../bind9-dnsutils_1%3a9.18.28-1~deb12u2_amd64.deb ...
Unpacking bind9-dnsutils (1:9.18.28-1~deb12u2) over (1:9.20.4-2) ...
dpkg: warning: downgrading bind9-libs:amd64 from 1:9.20.4-2 to
1:9.18.28-1~deb12u2
Preparing to unpack .../bind9-libs_1%3a9.18.28-1~deb12u2_amd64.deb ...
Unpacking bind9-libs:amd64 (1:9.18.28-1~deb12u2) over (1:9.20.4-2) ...
Setting up bind9-libs:amd64 (1:9.18.28-1~deb12u2) ...
Setting up bind9-utils (1:9.18.28-1~deb12u2) ...
Setting up bind9 (1:9.18.28-1~deb12u2) ...
Installing new version of config file /etc/init.d/named ...
Stopping domain name service...: namedrndc: connect failed: 127.0.0.1#953:
connection refused
.
Starting domain name service...: named.
Setting up bind9-host (1:9.18.28-1~deb12u2) ...
Setting up bind9-dnsutils (1:9.18.28-1~deb12u2) ...
Processing triggers for man-db (2.13.0-1) ...
Processing triggers for libc-bin (2.40-4) ...
Press Return to continue, 'q' followed by Return to quit.
am64:/usr/src/linux# resolvconf -l
# resolv.conf from lo.named
nameserver 127.0.0.1
# resolv.conf from eth0.dhclient
domain lan
nameserver 10.1.1.1
# resolv.conf from original.resolvconf
domain lan
search lan
nameserver 10.1.1.1
When I upgraded bind9 again:
Preparing to unpack .../bind9_1%3a9.20.4-3_amd64.deb ...
Unpacking bind9 (1:9.20.4-3) over (1:9.18.28-1~deb12u2) ...
Preparing to unpack .../bind9-utils_1%3a9.20.4-3_amd64.deb ...
Unpacking bind9-utils (1:9.20.4-3) over (1:9.18.28-1~deb12u2) ...
Preparing to unpack .../bind9-host_1%3a9.20.4-3_amd64.deb ...
Unpacking bind9-host (1:9.20.4-3) over (1:9.18.28-1~deb12u2) ...
Preparing to unpack .../bind9-dnsutils_1%3a9.20.4-3_amd64.deb ...
Unpacking bind9-dnsutils (1:9.20.4-3) over (1:9.18.28-1~deb12u2) ...
Preparing to unpack .../bind9-libs_1%3a9.20.4-3_amd64.deb ...
Unpacking bind9-libs:amd64 (1:9.20.4-3) over (1:9.18.28-1~deb12u2) ...
Setting up bind9-libs:amd64 (1:9.20.4-3) ...
Setting up bind9-utils (1:9.20.4-3) ...
Setting up bind9 (1:9.20.4-3) ...
Installing new version of config file /etc/init.d/named ...
Stopping domain name service...: namedrndc: connect failed: 127.0.0.1#953:
connection refused
.
Starting domain name service...: named.
Setting up bind9-host (1:9.20.4-3) ...
Setting up bind9-dnsutils (1:9.20.4-3) ...
Processing triggers for man-db (2.13.0-1) ...
Processing triggers for libc-bin (2.40-4) ...
Press Return to continue, 'q' followed by Return to quit.
q
am64:/usr/src/linux# resolvconf -l
# resolv.conf from eth0.dhclient
domain lan
nameserver 10.1.1.1
# resolv.conf from original.resolvconf
domain lan
search lan
nameserver 10.1.1.1
* What was the outcome of this action?
So it seems that several updates ago, bind9 stopped calling resolvconf when
started and stopped.
both /etc/default/bind9 and /etc/default/named have:
RESOLVCONF=yes
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: trixie/sid
APT prefers experimental
APT policy: (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.11.0 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages bind9 depends on:
ii adduser 3.137
ii bind9-libs 1:9.20.4-3
ii bind9-utils 1:9.20.4-3
ii debconf [debconf-2.0] 1.5.87
ii dns-root-data 2024071801
ii init-system-helpers 1.67devuan1
ii iproute2 6.12.0-1
ii libc6 2.40-4
ii libcap2 1:2.66-5+b1
ii libelogind-compat [libsystemd0] 255.5-3
ii libfstrm0 0.6.1-1+b3
ii libjemalloc2 5.3.0-2+b2
ii libjson-c5 0.18+ds-1
ii liblmdb0 0.9.31-1+b2
ii libmaxminddb0 1.11.0-1
ii libnghttp2-14 1.64.0-1
ii libprotobuf-c1 1.4.1-1+b3
ii libssl3t64 3.3.2-2
ii libuv1t64 1.48.0-7
ii libxml2 2.12.7+dfsg+really2.9.14-0.2+b1
ii lsb-base 11.6
ii netbase 6.4
ii sysvinit-utils [lsb-base] 3.11-1devuan1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
bind9 recommends no packages.
Versions of packages bind9 suggests:
pn bind-doc <none>
ii bind9-dnsutils [dnsutils] 1:9.20.4-3
ii resolvconf 1.92
pn ufw <none>
-- Configuration Files:
/etc/default/named changed:
RESOLVCONF=yes
OPTIONS="-u bind"
-- debconf-show failed
