Ubuntu
network-manager package

Problem with DNS resolution after suspend

Bug #1633912 reported by Jonas Schwabe on 2016-10-16

This bug report is a duplicate of: Bug #1639776: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface. Edit Remove

This bug affects 10 people

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend).

Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service.

I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 16 21:01:09 2016
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-09-28 (18 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
default via 192.168.0.1 dev wlp58s0 proto static metric 600
169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1
192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.2.4 connected started full enabled enabled enabled enabled enabled

Tags:

Revision history for this message

Jonas Schwabe (jonas-schwabe) wrote on 2016-10-16:

CRDA.txt Edit (251 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (8.4 KiB, text/plain; charset="utf-8")
IpAddr.txt Edit (2.1 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (658 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (121.7 KiB, text/plain; charset="utf-8")
NetDevice.br-541a0f9bec93.txt Edit (408 bytes, text/plain; charset="utf-8")
NetDevice.docker0.txt Edit (376 bytes, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (248 bytes, text/plain; charset="utf-8")
NetDevice.veth2993121.txt Edit (393 bytes, text/plain; charset="utf-8")
NetDevice.veth6645f0d.txt Edit (393 bytes, text/plain; charset="utf-8")
NetDevice.veth97d4973.txt Edit (392 bytes, text/plain; charset="utf-8")
NetDevice.wlp58s0.txt Edit (948 bytes, text/plain; charset="utf-8")
NetworkManager.conf.txt Edit (75 bytes, text/plain; charset="utf-8")
PciNetwork.txt Edit (662 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (136 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (279.4 KiB, text/plain; charset="utf-8")
nmcli-con.txt Edit (3.0 KiB, text/plain; charset="utf-8")
nmcli-dev.txt Edit (1.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Jonas Schwabe (jonas-schwabe) wrote on 2016-10-16:

▶ sudo killall dnsmasq
Works as well, afterwards things work again.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-10-18:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status:	New → Confirmed

Revision history for this message

Plurtu (plurtu) wrote on 2016-10-19:

I've had the same problem on two computers since upgrading from 16.04 to 16.10, in both cases killing dnsmasq after the first suspend fixes it and it stays fixed after subsequent suspends.

Revision history for this message

Vladimir (thunder27) wrote on 2016-10-20:

dhclient.conf Edit (1.7 KiB, text/plain)

Revision history for this message

Vladimir (thunder27) wrote on 2016-10-20:

Hi, I don't know, if it is a same bug, but i have problems with wired connection after boot too. When I turn on my computer (PC, not laptop) I cannot access some https sites in firefox or chromium (but in chrome i can). Or some extentions for Gnome shell (like weather) doesn't connect to server to receive data from servers.

If i use
sudo killall dhclient

then network works correct and everything is ok, but only for some time (sometimes few minutes, sometimes hour, sometimes more). Then sometimes mess up and i must use same command to repair my connection.

I made a new profile in network manager and if i use command:
nmcli con up Drátové\ připojení\ 1
it work properly too, but same as with killall dhclient (so not permanently). So something with NM or dhclient is wrong.

My Mobo: Asus Z170 Pro Gaming
Ubuntu Gnome 16.10 64bit

If you want some logs, just write and i will add attachments here for you

Sorry, attachment of dhclient.conf added in #5

Revision history for this message

Plurtu (plurtu) wrote on 2016-10-22:

More people with the same problem:
https://ubuntuforums.org/showthread.php?t=2340142

Workaround: Edit /etc/NetworkManager/NetworkManager.conf and remove the line "dns=dnsmasq".

Revision history for this message

Jonas Schwabe (jonas-schwabe) wrote on 2016-10-22: Re: [Bug 1633912] Re: Problem with DNS resolution after suspend

Workaround worked for me and fixed multiple issues! I can use DNS while
being connected to a VPN again :)

Plurtu <email address hidden> schrieb am Sa., 22. Okt. 2016, 10:25:

> More people with the same problem:
> https://ubuntuforums.org/showthread.php?t=2340142
>
> Workaround: Edit /etc/NetworkManager/NetworkManager.conf and remove the
> line "dns=dnsmasq".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633912
>
> Title:
> Problem with DNS resolution after suspend
>
> Status in network-manager package in Ubuntu:
> Confirmed
>
> Bug description:
> I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
> have network issues, one time I was not able to connect to a wifi
> network (might report another bug if this occurees again, but maybe it
> is related, as in network-manager is in some broken state after
> suspend).
>
> Here is whats happening pretty often: After resume from suspend I have
> a solid network connection, no problem to ping machines in LAN or on
> the internet. But DNS resolution is broken until I restart the
> network-manager service.
>
> I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
> should be in there.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: network-manager 1.2.4-0ubuntu1
> ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
> Uname: Linux 4.8.0-22-generic x86_64
> ApportVersion: 2.20.3-0ubuntu8
> Architecture: amd64
> CurrentDesktop: Unity
> Date: Sun Oct 16 21:01:09 2016
> IfupdownConfig:
> # interfaces(5) file used by ifup(8) and ifdown(8)
> auto lo
> iface lo inet loopback
> InstallationDate: Installed on 2016-09-28 (18 days ago)
> InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
> IpRoute:
> default via 192.168.0.1 dev wlp58s0 proto static metric 600
> 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000
> 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
> linkdown
> 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src
> 172.18.0.1
> 192.168.0.0/24 dev wlp58s0 proto kernel scope link src
> 192.168.0.118 metric 600
> NetworkManager.state:
> [main]
> NetworkingEnabled=true
> WirelessEnabled=true
> WWANEnabled=true
> SourcePackage: network-manager
> UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
> nmcli-nm:
> RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING
> WIFI-HW WIFI WWAN-HW WWAN
> running 1.2.4 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/1633912/+subscriptions
>

Workaround worked for me and fixed multiple issues! I can use DNS while
being connected to a VPN again :)

Plurtu <1633912@bugs.launchpad.net> schrieb am Sa., 22. Okt. 2016, 10:25:

> More people with the same problem:
> https://ubuntuforums.org/showthread.php?t=2340142
>
> Workaround: Edit /etc/NetworkManager/NetworkManager.conf and remove the
> line "dns=dnsmasq".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633912
>
> Title:
>   Problem with DNS resolution after suspend
>
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
>   have network issues, one time I was not able to connect to a wifi
>   network (might report another bug if this occurees again, but maybe it
>   is related, as in network-manager is in some broken state after
>   suspend).
>
>   Here is whats happening pretty often: After resume from suspend I have
>   a solid network connection, no problem to ping machines in LAN or on
>   the internet. But DNS resolution is broken until I restart the
>   network-manager service.
>
>   I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
>   should be in there.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: network-manager 1.2.4-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Oct 16 21:01:09 2016
>   IfupdownConfig:
>    # interfaces(5) file used by ifup(8) and ifdown(8)
>    auto lo
>    iface lo inet loopback
>   InstallationDate: Installed on 2016-09-28 (18 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   IpRoute:
>    default via 192.168.0.1 dev wlp58s0  proto static  metric 600
>    169.254.0.0/16 dev br-541a0f9bec93  scope link  metric 1000
>    172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1
> linkdown
>    172.18.0.0/16 dev br-541a0f9bec93  proto kernel  scope link  src
> 172.18.0.1
>    192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src
> 192.168.0.118  metric 600
>   NetworkManager.state:
>    [main]
>    NetworkingEnabled=true
>    WirelessEnabled=true
>    WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
>   nmcli-nm:
>    RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI     WWAN-HW  WWAN
>    running  1.2.4    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/1633912/+subscriptions
>