>From the syslog
Jun 15 21:42:27 paul-Latitude-E6420 NetworkManager[1002]: <info> Internal IP4
DNS: 172.23.170.10
Jun 15 21:42:27 paul-Latitude-E6420 NetworkManager[1002]: <info> Internal IP4
DNS: 172.23.4.10
Jun 15 21:42:27 paul-Latitude-E6420 NetworkManager[1002]: <info> DNS Domain:
'topcon.com'
[...]
Jun 15 21:42:28 paul-Latitude-E6420 dnsmasq[4897]: using nameserver
192.168.1.254#53
Jun 15 21:42:28 paul-Latitude-E6420 dnsmasq[4897]: using nameserver
172.23.170.10#53 for domain 0.168.192.in-addr.arpa
Jun 15 21:42:28 paul-Latitude-E6420 dnsmasq[4897]: using nameserver
172.23.170.10#53 for domain 16.172.in-addr.arpa
Jun 15 21:42:28 paul-Latitude-E6420 dnsmasq[4897]: using nameserver
172.23.170.10#53 for domain 10.in-addr.arpa
Jun 15 21:42:28 paul-Latitude-E6420 dnsmasq[4897]: using nameserver
172.23.170.10#53 for domain 254.169.in-addr.arpa
Jun 15 21:42:28 paul-Latitude-E6420 dnsmasq[4897]: using nameserver
172.23.170.10#53 for domain 23.172.in-addr.arpa
Jun 15 21:42:28 paul-Latitude-E6420 dnsmasq[4897]: using nameserver
172.23.170.10#53 for domain topcon.com
Notice that only the first nameserver address is used. This is bug
#1072899. As a result of this, if 172.23.170.10 is down 172.23.4.10
won't be tried.
Was the first nameserver nonresponsive when this report was originally
filed? That along with bug #1072899 would explain the malfunction
originally reported.
** Changed in: network-manager-vpnc (Ubuntu)
Status: Confirmed => Incomplete
--
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 connected but private-network names cannot be resolved; bypassing
the local forwarding nameserver fixes it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1013646/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
