Comment 4 for bug 262042

The problem was solved after removing the package resolvconf.

The root of the problem seems to be that resolvconf and network-manager conflict in writing to /etc/resolv.conf. resolvconf seems to get priority here but does not seem to have all relevant information, which network-manger obviously has, even though I connect through KVPNC.

It's strange, but this seems to be the only logical explanations, since network-manager has always produced a correct /etc/resolv.conf after the removal of resolvconf.

I've also switched from network-manager-gnome to network-manager-kde once it has been adapted to the new API. However, the problem persisted until I removed resolvconf.

So is this a bug in resolvconf, kdenetwork, both or something else entirely? Someone with more understanding of the matter should please correct the affected package, if necessary.