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.named
And if resolvconf sees that file, it uses it and ignores the other files. Therefore it looks like the flag does not work.
After a reboot, the /run/... being in RAM, it will have been wiped out and thus it won't include the lo.named anymore.
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.named
And if resolvconf sees that file, it uses it and ignores the other files. Therefore it looks like the flag does not work.
After a reboot, the /run/... being in RAM, it will have been wiped out and thus it won't include the lo.named anymore.