I'm not a packaging expert, so excuse me if I've gotten something wrong here,
but the commit which "removed obsolete empty zone-files" was
d3e8623f7466f28f5a8df6a9136eb4d1d0d2d2af in salsa.
But:
* debian/extras/etc/named.conf.default-zones still exists and looks like this:
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/usr/share/dns/root.hints";
};
* On the one hand, debian/bind9.install includes this line:
...
debian/extras/etc/* /etc/bind/
...
* While on the other hand, debian/bind9.maintscript includes this line:
...
rm_conffile /etc/bind/named.conf.default-zones 1:9.20.5-1~
...
* After a fresh install on sid (1:9.20.11-1, so same version as Trixie):
$ ls -al /etc/bind
...
-rw-r--r-- 1 root bind 412 Jul 16 17:08 named.conf
-rw-r--r-- 1 root bind 116 Jul 16 17:08 named.conf.default-zones
-rw-r--r-- 1 root bind 42 Jul 16 17:08 named.conf.local
-rw-r--r-- 1 root bind 43 Jul 16 17:08 named.conf.options
-rw-r----- 1 bind bind 100 Jul 27 02:03 rndc.key
$ cat /etc/bind/named.conf
...
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
Was it really intentional to remove /etc/named.conf.default-zones? (And if so,
why does bind9 depend on the dns-root-data package?)
