Name resolution stops working after resume from suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dnsmasq |
Fix Released
|
Unknown
|
|||
dnsmasq (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working.
* Also affect Xenial (Unity/
After resuming, systemd-resolved is running and libnss-resolve is installed, but /etc/resolv.conf contains 127.0.1.1 as the the only name server. The dnsmasq-base package is installed since it is pulled in by both network-manager and lxc1, and both NM and libvirt have spawned instances of dnsmasq:
> 1155 pts/2 S+ 0:00 grep dnsmasq
> 2724 ? S 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=
> 2992 ? S 0:00 /usr/sbin/dnsmasq --conf-
> 2993 ? S 0:00 /usr/sbin/dnsmasq --conf-
> 22879 ? S 0:00 /usr/sbin/dnsmasq --no-resolv --keep-
Let me know if you need any extra info.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libnss-resolve 231-9git1
ProcVersionSign
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 7 13:52:40 2016
InstallationDate: Installed on 2015-07-22 (443 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)
tags: | added: nm-improvements |
Changed in dnsmasq: | |
status: | Unknown → Fix Released |
With NetworkManager we switched back to the "dnsmasq" plugin, so it is indeed correct that resolv.conf only contains 127.0.1.1. It also does that without suspending.
So what is actually not working?