The change introduced[1] in resolveconf-1.78ubuntu4 over 1.78ubuntu2
affects *when* resolvconf service starts; but does not affect the
runtime code and is not involved in any of the runtime action of the
resolvconf service. I'm marking the resolvconf task as invalid.
If you feel that the resolvconf change to when resolvconf service starts during
boot affects the runtime DNS settings, please do re-open against resolvconf and
include:
a. systemctl status resolvconf
b. contents of /etc/resolv.conf
1. diff -Nru resolvconf-1.78ubuntu2/debian/resolvconf.service
resolvconf-1.78ubuntu4/debian/resolvconf.service
--- resolvconf-1.78ubuntu2/debian/resolvconf.service 2015-06-03
15:58:21.000000000 -0500
+++ resolvconf-1.78ubuntu4/debian/resolvconf.service 2016-12-07
03:03:18.000000000 -0600
@@ -2,7 +2,8 @@
Description=Nameserver information manager
Documentation=man:resolvconf(8)
DefaultDependencies=no
-Before=networking.service
+Before=network-pre.target
+Wants=network-pre.target
** Changed in: resolvconf (Ubuntu)
Status: Confirmed => Invalid
** Changed in: resolvconf (Ubuntu)
Assignee: Ryan Harper (raharper) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1671606
Title:
DNS server from vpn connection is not being used after network-manager
upgrade to 1.2.6-0ubuntu0.16.04.1
Status in network-manager package in Ubuntu:
Confirmed
Status in resolvconf package in Ubuntu:
Invalid
Bug description:
I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
LTS. After recent upgrade of network-manager:amd64 from version
1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
resolution of VPN's server hostnames does not work. Roll back to
version 1.2.2-0ubuntu0.16.04.4 solves the problem.
Steps for reproducing:
1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to
version 1.2.6-0ubuntu0.16.04.1
2. connect to VPN via network-manager applet
3. nslookop servername.internal --> ** server can't find servername.internal:
NXDOMAIN
4. disconnect from VPN via network-manager applet
5. roll back network-manager via command: sudo apt-get install
network-manager=1.2.2-0ubuntu0.16.04.4
6. restart network-manager via sudo service network-manager restart
7. connect to VPN via network-manager applet
8. nslookop servername.internal --> the server is resolved correctly
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 9 19:49:55 2017
InstallationDate: Installed on 2015-10-05 (520 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.2.6 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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
