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.
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.