got the same problem caused by a manual vpnc connection and Networkmanager on hardy(kubuntu). i wouldn't do that but knetworkmanager 0.7 seems to have lost a lot of functionality and usability since 0.2.2 (inlcuding vpnc connections). I found out that deleting /etc/resolvconf/run/interface/tun0, which contains all wrong entries messing up /etc/resolv.conf, fixed Gthe symptoms. So resolvconf doesn't seem to check whether the interface tun0 is up or not.
got the same problem caused by a manual vpnc connection and Networkmanager on hardy(kubuntu). i wouldn't do that but knetworkmanager 0.7 seems to have lost a lot of functionality and usability since 0.2.2 (inlcuding vpnc connections). I found out that deleting /etc/resolvconf /run/interface/ tun0, which contains all wrong entries messing up /etc/resolv.conf, fixed Gthe symptoms. So resolvconf doesn't seem to check whether the interface tun0 is up or not.