@gatoguan-os : You must have been speaking about the work-around here? https://bugs.launchpad.net/network-manager-applet/+bug/1633874
Is the above really a duplicate or not? Lately, I have not even been able to get that work-around (in the link above) to work in 16.04. Also, this is a related bug, but not exactly what's reported here (it might be a ramification of what's reported here): https://bugs.launchpad.net/network-manager-applet/+bug/1633877 Right? I hope all these ramifications get fixes. @tmus : I wonder if 1.4.4-1ubuntu3 will make it into 16.04 (Long term release). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken Status in NetworkManager-OpenVPN: New Status in network-manager-vpnc: New Status in network-manager package in Ubuntu: Confirmed Bug description: network-manager: 1.2.4-0ubuntu1 Yakkety appears to have switched back from resolved to dnsmasq, but it seems server priority/order is broken. Example: In split DNS setups, connecting to VPN will not cause us to query the DNS provided by the VPN first (or only), which should be the proper way to resolve names in that case. Say server.example.com in the public DNS resolves to a.a.a.a and in the private DNS resolves to b.b.b.b. Stuff would work from my normal internet-connection, but connection to VPN would cause stuff to misbehave. I expect to hit the b.b.b.b address but since my normal LAN DNS is being used first, I'm really hitting a.a.a.a. Please let me know how to proceed - Hopefully this can be fixed in time for release. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
