Comment 35 for bug 96260

Revision history for this message
Mark A. Hershberger (hexmode) wrote :

I am having this problem with a VPN that I set up.

This is a VPN for the express purpose of connecting to a single host in a remote country behind a firewall. Since this is essentially a management VPN for one (more later?) machine, I absolutely do not want to set up a nameserver. I would prefer to use a local nameserver.

Another use case: A co-worker and former Yahoo! employee told me that Y! put all their private names on their public DNS. So a Y! VPN user could continue using the local DNS server even after they connected to the VPN. I've no idea if Yahoo! still does this, but that would certainly be another use case for fixing this bug.

As it is it doesn't look like Hardy has the fix (http://packages.ubuntu.com/network-manager-openvpn) since the version in Hardy is the same as in Gutsy. I'll look around for a PPA with a fixed package and if one doesn't exist I'll publish a fixed package in my PPA.