Thanks for the research on this guys. I had been a idle spectator to the systemd controversies, but didn't realize that I might be bumping up into those choices in a real way myself.
Attached is my systemd-resolve --status. I imagine it shows what you are talking about. And I also went ahead and tried to switch to dnsmasq and see if that fixed the problem. Unfortunately, it seems that I may need to do something different to actually shut down systemd-resolved. I tried those instructions with a restart, and systemd-resolved was still running. I tried those instructions without a restart, but either systemd-resolved started up again by itself or perhaps by me reconnecting to my VPN via network-manager. I did confirm that systemd- resolved was at some point disabled after executing the commands in step #2 of those instructions, but not sure what started it up again. Correct me if I'm wrong, but DNS leaking via systemd related issues should be a pretty high priority bug, correct? If it's not the case, and your sense is that there are a lot of technical or political hurdles to this being corrected, perhaps it makes sense for me to return to 16.04 in the meantime. ** Attachment added: "sys.status" https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1685391/+attachment/4868227/+files/sys.status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685391 Title: DNS leak in Xubuntu 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1685391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
