Package: bind9
Version: 1:9.19.21-1+b1
Severity: minor
Dear Maintainer,
* What led up to the situation?
Black Lives Matter, ISC and other updates with the times, etc.,
some older Debian specific files that haven't quite caught up yet.
* What outcome did you expect instead?
Hoping these files will be appropriately updated soon. :-)
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
By between BIND 9.11.5 Debian buster 10 and BIND 9.16.48 Debian bullseye
11, preferred terminology had generally shifted from master/masters to
primary/primaries, and from slave/slaves to secondary/secondaries.
Debian bind9 still contains at least two Debian specific included files
that aren't yet caught up on that, and should have the references to
master updated to instead use primary:
$ (cd /etc/bind && find * -type f ! -size 0 -exec grep -a -F -n -e \
> master \{\} /dev/null \; 2>>/dev/null)
(cd /etc/bind && find * -type f ! -size 0 -exec grep -a -F -n -e master \{\}
/dev/null \; 2>>/dev/null)
named.conf.default-zones:11: type master;
named.conf.default-zones:16: type master;
named.conf.default-zones:21: type master;
named.conf.default-zones:26: type master;
zones.rfc1918:1:zone "10.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:3:zone "16.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:4:zone "17.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:5:zone "18.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:6:zone "19.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:7:zone "20.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:8:zone "21.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:9:zone "22.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:10:zone "23.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:11:zone "24.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:12:zone "25.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:13:zone "26.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:14:zone "27.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:15:zone "28.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:16:zone "29.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:17:zone "30.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:18:zone "31.172.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
zones.rfc1918:20:zone "168.192.in-addr.arpa" { type master; file
"/etc/bind/db.empty"; };
Thanks for your attention to this matter.
