I believe this is the same root problem as I'm seeing in Karmic. The vpnc generated nameservers get added to the *end* of the resolv.conf list, rather than the beginning. Thus, nameserver requests for hosts reachable over the VPN connection fail because the non-VPN nameservers respond first saying that the address does not exist.
A workaround is to reorder the entries in resolv.conf so that the vpnc generated nameserver is first. It is tedious to do this by hand every time one connects via VPN. This was not an issue in Jaunty (for me, at least). The real fix is to have resolvconf or whatever writes the resolv.conf file to put the vpnc generated nameserver first automatically. An even better fix would be to support split DNS for hostname resolution. -- vpnc issue with /etc/resolv.conf prevents connection https://bugs.launchpad.net/bugs/297796 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
