DNS search domain not removed from resolv.conf on disconnect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
Unknown
|
Unknown
|
|||
network-manager (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
resolvconf (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When I connect to a wireless network that sets a DNS search domain name via DHCP, the line 'search <domain>' is added to /etc/resolv.conf as expected. But if I then disconnect and connect to a different network, it is not removed from resolv.conf. If the second network also sets a search domain name, that one gets appended to resolv.conf along with the first one, and so on. Depending on the network, this can cause DNS leaks, name resolution failures, or other misbehavior.
To be sure this wasn't some kind of user configuration issue, I reproduced this on the artful daily live image (artful-
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu3
ProcVersionSign
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 10:34:22 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 172.20.20.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
wlp3s0 wifi connected /org/freedeskto
enp0s31f6 ethernet unavailable /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.8.2 connected started full enabled enabled enabled enabled enabled
Changed in resolvconf (Ubuntu): | |
status: | New → Confirmed |
Changed in network-manager (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
Hi,
I can confirm this bug.
This is really annoying as it breaks VPN connection here