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
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
** Summary changed:
- Bind is not configured correctly on upgrade
+ Bind is not configured correctly on upgrade (resolvconf integration)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Summary changed:
- Bind is not configured correctly on upgrade
+ Bind is not configured correctly on upgrade (resolvconf integration)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996088
Title:
** Changed in: bind9 (Ubuntu)
Importance: Undecided = Medium
** Changed in: bind9 (Ubuntu)
Status: New = Confirmed
--
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/996088
** Changed in: bind9 (Ubuntu)
Importance: Undecided = Medium
** Changed in: bind9 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996088
Title:
Bind is not
--
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/996088
Title:
Bind is not configured correctly on upgrade
To manage notifications about this bug go to:
** Description changed:
On an upgrade to Precise, bind was not correctly reconfigured, resulting
in a failure to resolve domain names.
- Solution was to reconfigure the bind9 package,
+ Solution was to dpkg-reconfigure the bind9 package, and turn off
+ resolvconf integration which was left
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996088
Title:
Bind is not configured correctly on upgrade
To manage notifications about this bug go to:
** Description changed:
On an upgrade to Precise, bind was not correctly reconfigured, resulting
in a failure to resolve domain names.
- Solution was to reconfigure the bind9 package,
+ Solution was to dpkg-reconfigure the bind9 package, and turn off
+ resolvconf integration which was left
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
12 matches
Mail list logo
