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 the problem seems to belongs to line 87 to 92 of bind9.postinst in the source package : db_get bind9/run-resolvconf if [ ! -z "$RET" ] && [ "$RET" = "true" ]; then echo "RESOLVCONF=yes" >> $config else echo "RESOLVCONF=no" >> $config fi I don't know what $RET refers to, perhaps it interacts with bind9.config? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933723 Title: bind9 registering itself with resolvconf but not set up to forward queries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/933723/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
