Package: bind9
Version: 1:9.9.5.dfsg-7
Severity: normal
Dear Maintainer,
following the upgrade to 1:9.9.5.dfsg-7 on Dec. 22nd named fails to load the
DLZ
zones from Samba:
Dec 29 10:43:07 verdandi named[2763]: Loading 'AD Zones' using driver dlopen
Dec 29 10:43:07 verdandi named[2763]: samba_dlz: started for DN
DC=ad,DC=microsult,DC=de
Dec 29 10:43:07 verdandi named[2763]: samba_dlz: starting configure
Dec 29 10:43:07 verdandi named[2763]: zone 10.16.172.in-addr.arpa/NONE: has 0
SOA records
Dec 29 10:43:07 verdandi named[2763]: zone 10.16.172.in-addr.arpa/NONE: has no
NS records
Dec 29 10:43:07 verdandi named[2763]: samba_dlz: Failed to configure zone
'10.16.172.in-addr.arpa.'
Dec 29 10:43:07 verdandi named[2763]: loading configuration: bad zone
Dec 29 10:43:07 verdandi named[2763]: exiting (due to fatal error)
Dec 29 10:43:07 verdandi named[2763]: samba_dlz: shutting down
This is strange, since samba reports the zones okay:
root@verdandi:~# samba-tool dns query localhost 10.16.172.in-addr.arpa. @ ALL
-U Administrator
Password for [AD\Administrator]:
Name=, Records=2, Children=0
SOA: serial=1, refresh=900, retry=600, expire=86400, minttl=3600,
ns=samba.ad.microsult.de., email=hostmaster.ad.microsult.de. (flags=600000f0,
serial=1, ttl=3600)
NS: samba.ad.microsult.de. (flags=600000f0, serial=1, ttl=3600)
A Wheezy Bind9 1:9.8.4.dfsg.P1-6+nmu2+deb7u3 runs perfectly on a replica server
in the same configuration (but with other samba_dlz plugin lib of course).
Syslog
on the Jessie machine has Bind9 exiting gracefully due to bind restart after
upgrading, but failing to come up with the described issue immediately
afterwards.
Inquiries to the samba mailing list (see: samba_dlz Failed to configure
reverse zone) did not yield any results. Although BIND_DLZ configuration of
a Samba AD DC is quite common, the issue seems to be unknown. This hints
at something broken in this particular Bind9 package.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages bind9 depends on:
ii adduser 3.113+nmu3
ii bind9utils 1:9.9.5.dfsg-7
ii debconf [debconf-2.0] 1.5.55
ii init-system-helpers 1.22
ii libbind9-90 1:9.9.5.dfsg-7
ii libc6 2.19-13
ii libcap2 1:2.24-6
ii libcomerr2 1.42.12-1
ii libdns100 1:9.9.5.dfsg-7
ii libgssapi-krb5-2 1.12.1+dfsg-16
ii libisc95 1:9.9.5.dfsg-7
ii libisccc90 1:9.9.5.dfsg-7
ii libisccfg90 1:9.9.5.dfsg-7
ii libk5crypto3 1.12.1+dfsg-16
ii libkrb5-3 1.12.1+dfsg-16
ii liblwres90 1:9.9.5.dfsg-7
ii libssl1.0.0 1.0.1j-1
ii libxml2 2.9.1+dfsg1-4
ii lsb-base 4.1+Debian13+nmu1
ii net-tools 1.60-26+b1
ii netbase 5.3
bind9 recommends no packages.
Versions of packages bind9 suggests:
pn bind9-doc <none>
ii dnsutils 1:9.9.5.dfsg-7
pn resolvconf <none>
pn ufw <none>
-- Configuration Files:
/etc/bind/named.conf.local changed:
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
include "/etc/bind/zones.private";
include "/var/lib/samba/private/named.conf";
zones.private is zones.rfc1918 w/o 172.16.0.0, since I use this net.
/var/lib/samba/private/named.conf is as created by Samba:
dlz "AD Zones" {
# For BIND 9.9.0
database "dlopen /usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_9.so";
};
-- debconf information:
bind9/different-configuration-file:
bind9/start-as-user: bind
bind9/run-resolvconf: false
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
