Thanks, Stéphane. It doesn't actually affect resolvconf — sorry if I gave that impression. Because it is only the "down" script that is run at the wrong time (it is currently run at pre-down time instead of post-down time), the effect of the bug is minor: it only means that named is listening on the address of an interface that has since been deconfigured. Of course, if the admin customizes the script, misled into thinking that it gets run at post-down time (as it apparently should be) then it could become a bit more serious.
** Summary changed: - /etc/network/if-down.d/bind9 doesn't work; should be /etc/network/if-post-down.d/bind9 + The "rndc reconfig" in /etc/network/if-down.d/bind9 should be in /etc/network/if-post-down.d/bind9 ** Description changed: The bind9 package includes /etc/network/if-down.d/bind9 which does "rndc reconfig". But this should only be done *after* the interface has been deconfigured not before. NetworkManager's /etc/NetworkManager/dispatcher.d/01ifupdown run-partses only /etc/network/if-up.d and /etc/network/if-post-down.d, so when an interface is deconfigured using NetworkManager the bind9 hook script doesn't get run at all; named does not notice that the interface has been deconfigured until its next poll (which happens every 60 minutes by default). - It looks to me as if /etc/network/if-down.d/bind9 should be moved to - /etc/network/if-post-down.d/. + It looks to me as if the "rndc reconfig" in /etc/network/if-down.d/bind9 + should be moved into /etc/network/if-post-down.d/. bind 9 1:9.8.1.dfsg.P1-4.2ubuntu3 ** Description changed: The bind9 package includes /etc/network/if-down.d/bind9 which does "rndc reconfig". But this should only be done *after* the interface has been deconfigured not before. NetworkManager's /etc/NetworkManager/dispatcher.d/01ifupdown run-partses only /etc/network/if-up.d and /etc/network/if-post-down.d, so when an interface is deconfigured using NetworkManager the bind9 hook script doesn't get run at all; named does not notice that the interface has been deconfigured until its next poll (which happens every 60 minutes by default). It looks to me as if the "rndc reconfig" in /etc/network/if-down.d/bind9 - should be moved into /etc/network/if-post-down.d/. + should be moved into /etc/network/if-post-down.d/bind9. bind 9 1:9.8.1.dfsg.P1-4.2ubuntu3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1087228 Title: The "rndc reconfig" in /etc/network/if-down.d/bind9 should be in /etc/network/if-post-down.d/bind9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1087228/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
