From the dpkg log, I see there was a prompt for updating /etc/bind/named.conf,
and you kept your own version of the file.
The new config file does not include the /etc/bind/named.conf.default-zones -
which does not exist anymore;
I would say this is a configuration problem, and thus not a bug.
The workaround for you would be removing the offending line from your
configuration:
-include "/etc/bind/named.conf.default-zones";
+include "/etc/bind/named.conf.root-hints";
(and of course adjust the referenced files if you have other
configuration changes)
I am marking this bug invalid.
Regardless, I didn't find the release-notes for bind9 on Ubuntu
mentioning this change, and I think this is worth documenting. Adding a
release-notes task for that.
** Changed in: bind9 (Ubuntu)
Status: New => Invalid
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2156138
Title:
package bind9 1:9.20.18-1ubuntu2.1 failed to install@2Fupgrade: old
bind9 package postinst maintainer script subprocess failed with exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2156138/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
