Comment 41 for bug 90681

Hello

I've been having similar problems and looking for a long time for a solution. Finally seems to have solved my problem.
I do not understand how different installed packages decide to modify /etc/resolv.conf and sometimes without consideration to each other. In my case, I use NetworkManager to manage my connections.

Simply put, the solution was to remove the package "resolvconf" and use "networkmanager" for wired, wireless and vpn.

If you are using vpn connections, configure it through network manager (nm) and not through some other utility. There's a vpn for networkManager you need to install first.
If you don't use the nm-vpn like I was, for a few minutes you have /etc/resolv.conf set up properly with the vpn dns , search and domain settings but sooner or later nm will overwrite your files and your vpn will be broken.
So, using vpnc from the command line or other vpn tools won't do.

I hope this helps others.

As a suggestion for Ubuntu packagers, when installing networkManager, resolvconf should be one of those conflicting packages. Of course, there's probably a better solution.

Cheers

Chahé