Comment 36 for bug 448095

Yeah I'm actually stunned that such a design failure is not acted upon by Ubuntu. Guess
they just capitalize on the work done by Debian, without having to do the hard work of
actually maintaining a distribution.

However this bug MUST sting on servers and 'old-school' people that use
/etc/network/interfaces instead of NetworkManager, not to mention all the HOWTOs on the
net that suggest solutions involving /etc/network/interfaces.

Just apply the new versions of resolvconf files attached to the bug and your problems will
be gone, at least until the upgrade to 10.04 :-/

I myself am moving to Debian ASAP

grtz,
Sander

On Sunday 07 February 2010 10:25:55 you wrote:
> Just to say I have this bug too. :(
>
> Symptom:
>
> After a reboot, /etc/resolv.conf contains only this:
>
> $ 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
> nameserver 10.18.4.3
> nameserver 10.18.4.1
>
> There is no search domain, yet I specified it in /etc/network/interfaces
> as follows:
>
> dns-nameservers 10.18.4.3 10.18.4.1
> dns-search blah.co.uk fudd.co.uk
>
>
> However, if I now issue the following command :
>
> $ sudo /etc/init.d/networking restart
>
> It fixes /etc/resolv.conf, as per this:
>
> $ 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 blah.co.uk fudd.co.uk
> nameserver 10.18.4.3
> nameserver 10.18.4.1
>
> Can't wait till this is fixed.