Public bug reported:
After the upgrade from yenial to yakkety, the internal DNS servers
(pushed by the openvpn server) are not being used by dnsmasq.
Symptom:
I connect via openvpn (called from network manager), the connection is
established successfully but INTERNAL hostnames cannot be resolved.
The system itself is using dnsmasq.
I then have to kill the running dnsmasq instance. After it's been
(automagically) restarted, internal DNS names can be resolved.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager-openvpn 1.1.93-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Oct 6 20:06:33 2016
InstallationDate: Installed on 2014-02-07 (972 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: Upgraded to yakkety on 2016-10-01 (5 days ago)
** Affects: network-manager-openvpn (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug yakkety
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1631095
Title:
pushed dns servers not being used
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1631095/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
