Unfortunately, this appears to be expected and wanted behavior. The
reason for this is that you can only go two different ways: either the
VPN's nameserver is set *above* the local nameserver so that VPN
connections will work automatically once connected to (the issue the
original reporter was referring to as not working, which apparently
should be fixed in releases after Jaunty (and IIRC fixed in Lucid for
sure)), or set the VPNs nameservers after local nameservers, which makes
internet access work fine even through a VPN, but causes issues if the
domain in use is resolvable with both types of nameservers.
There is no way to please everybody unless using DNS caching. This is
planned for NM, but currently does not really have a roadmap that I know
of.
In other words, Eeqmcsq, for your system to work as you expect you will
need to upgrade to Lucid or later, so that you end up on NetworkManager
0.8 or later.
David, please file a separate bug for your issue and don't forget to
attach resolv.conf as it is written on your system, as well as a
snapshot of the routes applied when you are connected to the network.
The exact domain name in use will also be required.
** Changed in: network-manager-vpnc (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/396387
Title:
Unable to resolve VPN names AND connect to the Internet
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/396387/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
