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