Upgrade to oneiric wiped my resolv.conf for static interface

It's doing this on every boot now.

My /etc/network/interfaces file looks like this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
broadcast 192.168.1.255
dns-nameservers 192.168.1.5
dns-search *********.com

Status changed to 'Confirmed' because the bug affects multiple users.

Same here. It appears that the packet 'resolvconf' had been removed from the system. Reinstalling it and doing a ifdown eth0 && ifup eth0 fixes the problem.
Maybe we did the upgrade at the wrong moment...

On Wednesday 12 October 2011 09:32:27 you wrote:
> Same here. It appears that the packet 'resolvconf' had been removed from the
> system. Reinstalling it and doing a ifdown eth0 && ifup eth0 fixes the
> problem. Maybe we did the upgrade at the wrong moment...

I uninstalled network manager and hard-coded resolv.conf. I don't know what
the "right" fix is.

I installed resolvconf and it doesn't create resolv.conf in boot

Same problem here :
- Upgrade to Oneiric erased my resolv.conf
- Following your instructions I installed "resolconf" package
- Resolvconf is supposed to merge what's in /etc/resolvconf/resolv.conf.d/ ; but it doesn't
- I still have no DNS resolution until I add my servers into /etc/resolv.conf
- Rebooting ersases resolf.conf

this is an release critical bug!

Simply an NO-GO-AT-ALL !

The oneiric Releas must not happpen containing this bug.

Unqualified rewrite resolv.conf is an deasater!

Also NEtwork Manager disobeys a chmod 444 /etc/resolv.conf !

Simply not trash !

Such a thing has to be tested bevore Release !

marking this one for fixing in oneiric-updates. NM should obviously not be managing resolv.conf when it's not managing any interfaces.

Julian or others affected: are there any interfaces on the affected system that should be handled by NetworkManager? eth0 is configured in /e/n/i; but should NM be managing a wireless device, for instance?

In my case, no, I only have one static interface. I have uninstalled NM and I'm happy again. However, something regressed since natty since the config in my comment #2 used to set resolv.conf for me.

Julian,

Was that with resolvconf installed? resolvconf doesn't appear to be responding correctly here: it seems it resets the /etc/resolvconf/run/interface directory when started and thus is missing the required files from NM and ifupdown, which could explain the issues.

I don't know if I had resolvconf installed before the upgrade, sorry. I know that it was not installed *after* though, as I installed it to try it out on oneiric. It didn't work!

I had not resolvconf installed (or it was uninstalled during the upgrade). As for the interface issue, I've only one, eth0, static.

Removing networkmanager also fixed the problem.

Only eth0 here too

I had not resolvconf package installed before I tries to fix the bug.
However, resolvconf does not work much better :

- The file /etc/resolvconf/resolv.conf.d/original contains my nameservers, but is not merged to my actual /etc/resolv.conf (and does not work for dns if not)

- I forced a "cat /etc/resolvconf/resolv.conf.d/original >> /etc/resolv.conf" at the end of /etc/network/if-up.d/000resolvconf but it doesnt merge, or if it does, it is overwriten afterwards by an empty resolv.conf.

Indeed, resolvconf doesn't appear to work properly here either, so cases with one or more devices unmanaged and some devices managed by NM fails -- there's just no easy way to know what to do with resolv.conf in such a case, even just saving on startup and restoring that file on stop is kind of clumsy; this case is really supposed to be covered by resolvconf -- I'll file a separate bug for that.

As for the case with NM installed (read: running) but not managing any devices, it really shouldn't be clobbering /etc/resolv.conf. Fortunately, that's relatively easy to fix. I'll upload an updated package that covers this shortly.

Hello Julian, or anyone else affected,

Accepted network-manager into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I upgraded to network-manager 0.9.1.90-0ubuntu5.
The fix works for me : my original resolv.conf file is kept after reboot.
I removed resolvconf packages which is useless in this case and didn't solve.
Thanks a lot for Mathieu and Martin.
Serge

+1 Serge Hartmann

+1 here. Just upgraded to 11.10, and my resolv.conf gets wiped on every reboot.

network-manager is 0.9.1.90-0ubuntu6

@FernanAguero : This should not happen until you have upgraded to the proposed package - which fixes the bug.
Which repository gives you this package revision ?

This bug was fixed in the package network-manager - 0.9.1.90-0ubuntu5

---------------
network-manager (0.9.1.90-0ubuntu5) oneiric-proposed; urgency=low

  * debian/patches/fix_reading_intlist-like_ssids_965d586.patch: Fix numeric
    SSIDs parsing; if there is no semicolon, except the file is in new format
    (so just a valid, all-nums SSID rather than a integer list). (LP: #874328)
  * debian/patches/lp862134_resolv_conf_updates.patch: don't update routing
    and DNS for unmanaged devices or devices transitioning to unmanaged; in an
    attempt to keep possibly correct resolv.conf contents and routes.
    (LP: #862134)
 -- Mathieu Trudel-Lapierre <email address hidden> Thu, 20 Oct 2011 07:36:41 -0400

This problem just started occurring again after latest update on Oneric and after reboot.

+1 also on Precise

In Precise you should have resolvconf installed and /etc/resolv.conf should be a symbolic link "../run/resolvconf/resolv.conf". Please read resolvconf(8).

You are right, sorry. It was not the same problem, and a reboot solved it anyway.