That's weird named.conf.default-zones got (I hope) properly removed in 1:9.20.5-1:
$ cat debian/bind9.maintscript mv_conffile /etc/default/bind /etc/default/named 1:9.13.6~ mv_conffile /etc/default/bind9 /etc/default/named 1:9.12.0~ mv_conffile /etc/init.d/bind /etc/init.d/named 1:9.13.6~ mv_conffile /etc/init.d/bind9 /etc/init.d/named 1:9.12.0~ rm_conffile /etc/apparmor.d/local/usr.sbin.named 1:9.11.4+dfsg-1~ rm_conffile /etc/bind/db.root 1:9.11.4+dfsg-3~ rm_conffile /etc/bind/db.local 1:9.20.5-1~ rm_conffile /etc/bind/db.0 1:9.20.5-1~ rm_conffile /etc/bind/db.127 1:9.20.5-1~ rm_conffile /etc/bind/db.255 1:9.20.5-1~ rm_conffile /etc/bind/db.empty 1:9.20.5-1~ rm_conffile /etc/bind/named.conf.default-zones 1:9.20.5-1~ rm_conffile /etc/bind/zones.rfc1918 1:9.20.5-1~ Do you have the full upgrade log? What was the previous version? Ondrej -- Ondřej Surý (He/Him) [email protected] > On 8. 7. 2025, at 13:37, Lucas Nussbaum <[email protected]> wrote: > > Package: bind9 > Version: 1:9.20.9-1 > Severity: serious > > I ran into the following when testing bookwork2trixie upgrades. > > Upgrading bind9 results in: > Setting up bind9 (1:9.20.9-1) ... > Installing new version of config file /etc/bind/named.conf ... > > Configuration file '/etc/bind/named.conf.default-zones' > ==> Deleted (by you or by a script) since installation. > ==> Package distributor has shipped an updated version. > What would you like to do about it ? Your options are: > Y or I : install the package maintainer's version > N or O : keep your currently-installed version > D : show the differences between the versions > Z : start a shell to examine the situation > The default action is to keep your current version. > *** named.conf.default-zones (Y/I/N/O/D/Z) [default=N] ? > > I did not delete that file. > > Lucas >
