This bug is not fixed!!
With 1:9.8.1.dfsg.P1-3, /etc/resolv.conf still always fallback to
127.0.0.1. If I uninstall bind9 and that I reboot my server, the
nameserver is correctly set to 192.168.1.1. But if I install bind9
1:9.8.1.dfsg.P1-3, it immediately overwrites /etc/resolv.conf with
OK, here is what happens :
RESOLVCONF=yes must be changed to RESOLVCONF=no in /etc/default/bind9 by
the user. The bind9 update won't change this default setting if it is
already set.
Therefore it might be important to make sure that this default setting
will be included in the final release.
OK definitively not fixed, RESOLVCONF=yes is added into
/etc/default/bind9 when the file is created for the first time by the
installation of bind9.. Which is exactly what this fix should have
prevented.
I can't go with a complete patch suggestion due to my restricted
knowledge in packaging, but
