network-manager-vpnc resolvconf conflict

[Dan]

Binary package hint: network-manager-vpnc

The vpnc plugin for network-manager wasn't updating /etc/resolv.conf although running vpnc from the CLI worked just fine. Numerous forums report the same issue. I found the resolution here:

  http://ubuntuforums.org/showthread.php?t=325581

The following fixed it for me:
   sudo apt-get remove resolvconf

resolvconf is installed by default at least on my Gutsy system

[Ondřej Hošek (ravu-al-hemio)]

I have found the culprit: /etc/resolvconf/update.d/libc, the script that takes the information from resolvconf and actually updates /etc/resolv.conf, is limited to three name servers. It takes information from the files in /etc/resolvconf/run/interface/, reading them in order as they are returned by /lib/resolvconf/list-records. This order is configured in /etc/resolvconf/interface-order. NetworkManager uses /etc/resolvconf/run/interface/NetworkManager, which has a surprisingly low priority -- it is caught by the "*" at the end of interface-order.

The fix, without removing resolvconf, is to add "NetworkManager" on a new line to /etc/resolvconf/interface-order right after the comment. resolvconf and its scripts will now take NetworkManager's opinion much more seriously than all the others'.

[Alexander Sack (asac)]

which lines in interface-order should be of lower prio to fix this?

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!