| 2012-12-06 12:00:52 |
Thomas Hood |
bug |
|
|
added bug |
| 2012-12-14 12:27:54 |
Yolanda Robla |
bind9 (Ubuntu): status |
New |
Opinion |
|
| 2012-12-14 12:28:00 |
Yolanda Robla |
bind9 (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2012-12-15 09:34:33 |
Thomas Hood |
bug |
|
|
added subscriber Yolanda Robla |
| 2012-12-17 15:20:29 |
Stéphane Graber |
bind9 (Ubuntu): status |
Opinion |
Triaged |
|
| 2012-12-17 15:20:33 |
Stéphane Graber |
bind9 (Ubuntu): importance |
Wishlist |
Medium |
|
| 2012-12-17 15:50:08 |
Thomas Hood |
summary |
/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 |
|
| 2012-12-17 15:51:17 |
Thomas Hood |
description |
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/.
bind 9 1:9.8.1.dfsg.P1-4.2ubuntu3 |
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/.
bind 9 1:9.8.1.dfsg.P1-4.2ubuntu3 |
|
| 2012-12-17 15:51:32 |
Thomas Hood |
description |
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/.
bind 9 1:9.8.1.dfsg.P1-4.2ubuntu3 |
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/bind9.
bind 9 1:9.8.1.dfsg.P1-4.2ubuntu3 |
|
