[Bug 374286] Re: Network Manager is erroneously overwriting resolv.conf

[Mike Pontillo]

Right, I used "eth100" because I didn't want to use a real interface on
your system.  I just want to see if resolvconf is working. If you
replace "eth100" with "NetworkManager", you simulate what Network
Manager does. (I don't recommend doing this)

When you install resolvconf, manually editing /etc/resolv.conf is no
longer supported. You have to write the entries into the standard input
when you execute /sbin/resolvconf, and you must tell resolvconf which
interface the entry is associated with.

If any part of the system is manually editing /etc/resolv.conf, the
whole process breaks and you could see unpredictable results.

But you're right, the whole process seems a bit fragile. If resolvconf
wasn't set up correctly when Network Manager first wrote the config
file, you'd still see the old one until (probably) the next boot.

Again, from the log, Network Manager clearly thinks it's telling
'resolvconf' about three DNS servers:

May  9 19:29:55 fshlinux NetworkManager: <info>    nameserver '192.168.1.56' 
May  9 19:29:55 fshlinux NetworkManager: <info>    nameserver '208.67.222.222' 
May  9 19:29:55 fshlinux NetworkManager: <info>    nameserver '208.67.220.220' 
...
May  9 19:29:56 fshlinux NetworkManager: <info>  (wlan0): writing resolv.conf to /sbin/resolvconf 

Maybe resolvconf has trouble when you pass it more than 1-2 servers? Or
maybe it's expecting to be called three times - once for each
nameserver?

It sounds like if you are still having a problem, this bug should likely
be reassigned to the 'resolvconf' package.

-- 
Network Manager is erroneously overwriting resolv.conf
https://bugs.launchpad.net/bugs/374286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs