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 t
Opinion is a closing state for things that won't get fixed, please avoid
using it unless you actually mean it :)
This is clearly a bug, describing a race condition causing problems with
essential part of Ubuntu (resolvconf), so I'm changing this to Triaged
and Medium (as it doesn't seem to be caus
This report has been downgraded to "wishlist opinion". Very well,
Yolanda, but please accompany that change with some sort of explanation.
Bind9's ifdown hook script does "rndc reconfig" which causes named to
notice changes that have been made. If the script is run *before* taking
down the interfa
All very well to classify this as a "wishlist opinion", but please
accompany that with some sort of reasoning.
Bind9's ifdown hook script does "rndc reconfig" which causes named to
notice changes that have been made. If the script is run *before* taking
down the interface then it is run when no ch
** Changed in: bind9 (Ubuntu)
Status: New => Opinion
** Changed in: bind9 (Ubuntu)
Importance: Undecided => Wishlist
--
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
Ti
