As I ran in this problem too, I wanted to mention one thing:
The RESOLVCONF=no parameter one can set in /etc/default/bind9 is NOT "in
effect" until you reboot.
I put "in effect" between quotes because it is, but bind9 will not
delete the file it created on boot:
/run/resolvconf/interface/lo.name
** Changed in: bind9 (Debian)
Status: Unknown => New
--
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/933723
Title:
bind9 registers itself with resolvconf even though it's unable
