Bind is not configured correctly on upgrade (resolvconf integration)

[Steve Conklin]

On an upgrade to Precise, bind was not correctly reconfigured, resulting in a failure to resolve domain names.

Solution was to dpkg-reconfigure the bind9 package, and turn off resolvconf integration which was left on on upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bind9 1:9.8.1.dfsg.P1-4
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Mon May 7 11:03:12 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 bind9utils 1:9.8.1.dfsg.P1-4
 apparmor 2.7.102-0ubuntu3
SourcePackage: bind9
UpgradeStatus: Upgraded to precise on 2012-01-03 (125 days ago)
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.options: 2012-03-11T22:48:21.929661

[Steve Langasek (vorlon)]

LaMont, this is related to bug #933723; we've turned resolvconf integration off by default, but in the upgrade case it's still on, which causes problems now that resolvconf is installed by default. Could we include a one-time upgrade check when upgrading to the version in 12.04 that checks whether the resolvconf debconf question has been seen, and if it hasn't been (i.e. we're using the automatic default), to turn off resolvconf integration on upgrade?

[Grandswiss (joerg-straube)]

My "named.conf" looked like this:
  include "/etc/bind/named.conf.options";
  include "/etc/bind/named.conf.local";
  include "/etc/bind/named.conf.default-zones";

I changed it statically to:
  include "/var/run/bind/named.options";
  include "/etc/bind/named.conf.local";
  include "/etc/bind/named.conf.default-zones";

Even better would be, to select the right include based on info in "/etc/default/bind"