VPN connected but private-network names cannot be resolved; bypassing the local forwarding nameserver fixes it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-vpnc (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
1. Using Ubuntu 12.04 64bit
2. network-
3. I expect that once connected to VPN, I should be able to access the servers within the private network.
4. The network manager reports that it has connected, however when I go to connect to the private servers, it fails
and a ping in the terminal returns "unknown host".
Upon further investigation and comparison with a working Ubuntu 11.10 system, I compared /etc/resolv.conf files.
The one that works had:
# Generated by NetworkManager
domain <domain>
search <domain>
nameserver <name server IP addr1>
nameserver <name server IP addr2>
nameserver <name server IP addr3>
Mine had:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search <domain>
Changed in network-manager-vpnc (Ubuntu): | |
status: | Expired → New |
There does not appear to be any obvious work around.