For those using OpenVPN, I discovered that there is a package named
'openvpn-systemd-resolvd' that finally resolved this issue for me.
Here's the synopsis for the package in the repo...
"This is a helper script designed to integrate OpenVPN with the
systemd-resolved service via DBus instead of
By far, the easiest and most effective workaround I've found is commenting out
"dns=dnsmasq" in "/etc/NetworkManager/NetworkManager.conf" as a few others have
suggested above.
Disappointing that this continues to be an ongoing problem.
--
You received this bug notification because you are a
Just an FYI, I have to downgrade both network-manager=1.2.2-0ubuntu0.16.04.4
and resolvconf=1.78ubuntu2. Doing one or the other would not fix the problem
on my system (Linux Mint Mate 18.1).
I'm using a PPTP tunnel.
--
You received this bug notification because you are a member of Ubuntu
Just did a fresh install of Mint Mate 18.2 onto a new machine. Same
problem exists. While connected to VPN DNS queries are leaking to non-
VPN interface.
This needs to be fixed!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Same problem on new XPS 13 9360 with Mint Mate 18.1 Serena 64-bit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574667
Title:
Mouse pointer occasionally jumps to the
I've done some additional testing and it seems as though both the
network manager and the resolvconf package need to be downgraded to get
to a working state. If either or both are at the latest revision
(resolvconf = 1.78ubuntu4 and/or network-manager =
1.2.6-0ubuntu0.16.04.1) name resolution
*** This bug is a duplicate of bug 1671606 ***
https://bugs.launchpad.net/bugs/1671606
I have a similar problem. I tried rolling back the network manager from
1.2.6-0ubuntu0.16.04.1 to 1.2.2-0ubuntu0.16.04.4. Oddly, it seemed to fix DNS
for a few minutes, but it reverted to not working.
More input...
I downgraded the network manager from 1.2.6-0ubuntu0.16.04.1 to
1.2.2-0ubuntu0.16.04.4. Oddly, name resolution seemed to work for a few
minutes, then resumed the previous behavior where it would use the dhcp
specified DNS.
I downgraded resolvconf from 1.78ubuntu4 to 1.78ubuntu2.
It looks like the resolvconf package was updated on my machine on 3/2/2017
also. Isn't resolvconf responsible for updating DNS info when something like a
DNS lease is obtained?
I'm pretty sure I didn't see the problem until after the network-manager
package was updated around 3/8/2017, but
network-manager:amd64 (1.2.2-0ubuntu0.16.04.4, 1.2.6-0ubuntu0.16.04.1)
I'm seeing a very similar problem, except I'm using a PPTP tunnel. I'm
on a Mint MATE 18.1 distro. On approximately 3/8/2017 the network
manager package was updated and about that time is when name resolution
stopped working
10 matches
Mail list logo