[Bug 933723] [NEW] resolvconf creating bogus resolv.conf file

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

We're noticing this on every server we're installing Precise dailys on
for sniff testing.

First, we use DHCP exclusively in the certification labs for assigning
IP info to machines.  So while Stefan Bader ran into this with his
static IP setup
(https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/923685) we're
seeing it with our dhcp set up.  This is new behaviour also, I do not
believe this was an issue in earlier Precise images, (alpha 2) so this
seems to have been introduced since then.

At some point, I assume during the install, the system /etc/resolv.conf
is created using information gathered from the dhcp server and it gets a
single entry that looks like this:

nameserver 10.XXX.XXX.XXX

However, as soon as resolvconf is installed, this all gets replaced by
the resolvconf files, and our working resolv.conf becomes
/etc/resolvconf/resolv.conf.d/original, which is ignored by resolvconf.

After this, we get a useless resolvconf file that points to localhost:

ubuntu at ubuntu:~$ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search example.org

Now, looking into /etc/resolvconf/resolv.conf.d, there are three files:
base, head and original.


ubuntu at ubuntu:/etc/resolvconf/resolv.conf.d$ cat base
ubuntu at ubuntu:/etc/resolvconf/resolv.conf.d$ cat head
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
ubuntu at ubuntu:/etc/resolvconf/resolv.conf.d$ cat original
nameserver 10.189.84.1
ubuntu at ubuntu:/etc/resolvconf/resolv.conf.d$ 

so right now, by default, resolvconf is breaking resolv.conf on dhcp
setups (this is epidemic across our test labs)

I CAN resolve (no pun intended) this by simply replacing
/etc/resolv.conf with /etc/resolvconf/resolv.conf.d/original but that's
only a very temporary bandaid and NOT desired as a resolution.

** Affects: bind9 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
resolvconf creating bogus resolv.conf file
https://bugs.launchpad.net/bugs/933723
You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu.