Comment 18 for bug 1629611
Revision history for this message
| Lonnie Lee Best (launchpad-startport) wrote | #18 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Bryn, thank for the suggested work around. However, it is not a workaround for me. My issue is that I have over 100 Remmina RDP desktop configurations saved that connect to numerous computers on different VPNs by computer name (not by ip address). However, I cannot ping those computers by name when I'm connected to their respective VPNs anymore like I could before recent Network Manger updates. My issue is described in detail here:
https:/
When you are connected to a VPN, your computer is suppose to check that virtual private network's DNS servers too, when it cannot find (on your local network) the computer-name you are you are trying to reach by name.
Network Manger gives you the opportunity to specify "Additional DNS Servers" for each connection you set up whether it be LAN, WiFi, or VPN. Yet Network manager now fails to queries those DNS servers in the proper order. It seems to just give up at the local DNS level when the other DNSs you've configured could certainly tell you the ip address of the computer name you are trying to reach if it were simply asked. It is not being ASKED.