Link to similar upstream bug report with title Please default to
RESOLVCONF=no (Upstream bug report #483098 is now being tracked in
Launchpad by wishlist bug #1091602 with title Please add resolvconf
hook script to generate dynamic forwarders list.)
** Bug watch added: Debian Bug tracker
I'm hoping to understand the status of this a bit better. I am still
having issues with my Ubuntu desktop. This seems to have occurred after
an upgrade and I've been struggling to find a solution. I am running
Ubuntu 12.04.1 LTS and my system is up-to-date.
Here is what my resolv.conf
Saivann,
1:9.8.1.dfsg.P1-3 changes the default value of the bind9/run-resolvconf
debconf setting to false -- but if that setting has already been set
to true by an earlier installation of the bind9 package then the
RESOLVCONF=yes will still get written to the config file until you
manually
This bug is not fixed!!
With 1:9.8.1.dfsg.P1-3, /etc/resolv.conf still always fallback to
127.0.0.1. If I uninstall bind9 and that I reboot my server, the
nameserver is correctly set to 192.168.1.1. But if I install bind9
1:9.8.1.dfsg.P1-3, it immediately overwrites /etc/resolv.conf with
OK, here is what happens :
RESOLVCONF=yes must be changed to RESOLVCONF=no in /etc/default/bind9 by
the user. The bind9 update won't change this default setting if it is
already set.
Therefore it might be important to make sure that this default setting
will be included in the final release.
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
This bug was fixed in the package bind9 - 1:9.8.1.dfsg.P1-3
---
bind9 (1:9.8.1.dfsg.P1-3) unstable; urgency=low
[Zlatan Todoric]
* fixed Serbian latin translation of debconf template. Closes:
#634951
[Peter Eisentraut]
* Add support for status action to lwresd init
** Branch linked: lp:ubuntu/bind9
--
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/933723
Title:
bind9 registering itself with resolvconf but not set up to forward
queries
To manage
People continue to report the problem that named registers 127.0.0.1
with resolvconf even though named is not set up to forward queries. So I
suppose that the upload promised in #6 should happen before Precise is
released.
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- resolvconf creating bogus resolv.conf file
+ bind9 registering itself with resolvconf but not set up to forward queries
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
10 matches
Mail list logo
