Public bug reported:
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.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629611
Title:
dns server priority broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
