David, if you can't connect by IP it's an issue with configuration, and very unlikely to be a bug (unless your vpn server is some brand new device that isn't supported).
Stephen, please file your own bug report. Using Kvpn is using a completely different method which will not be affected by the same bugs, but we can't know about them and fix them unless you file the bug reports for your own system, since everyone's configuration is different. Paul, as per above, only subdomains of topcon.com will get resolved, are you using those names to try to reach the private servers? The in-addr.arpa entries are there for reverse resolution, and generally not to be concerned with -- they will do the match from IP to name (instead of from name to IP to get to reach the systems). You can try to ping and access servers by IP address, this should always be possible. If it's not, then there would be another thing that changed rather than DNS that affects your VPN connections. As for the DNS; try to resolve hostnames under topcon.com normally; and again using "dig <domain name> @<the other nameserver from syslog that isn't listed in nm-dns-dnsmasq.conf>". Perhaps it's just that one of the DNS servers isn't responding properly. While at it, could you please attach the output of 'ip route' ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013646 Title: VPN network connects but cannot access servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1013646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
