Public bug reported:
After a while / after resume from suspend, the system becomes unable to
respond to DNS queries, with the following output for example:
$ nslookup google.com 127.0.1.1
Server: 127.0.1.1
Address: 127.0.1.1#53
** server can't find google.com: REFUSED
This is on an up to date yakkety install. Changing resolv.conf to use 8.8.8.8,
or restarting network-manager appears to fix this, at least until it recurs
again.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
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: GNOME
Date: Sat Oct 1 21:28:51 2016
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-08-21 (407 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
default via 192.168.1.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev docker0 scope link metric 1000 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric
600
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
docker0 bridge connected
/org/freedesktop/NetworkManager/Devices/1 docker0
63f0b05b-f699-4a68-81ce-f62d2c1a247d
/org/freedesktop/NetworkManager/ActiveConnection/0
wlp3s0 wifi connected
/org/freedesktop/NetworkManager/Devices/4 HOME-1622-5
6df3f2f0-fb86-43b5-802a-d59bc5734be3
/org/freedesktop/NetworkManager/ActiveConnection/2
24:DA:9B:B9:09:0E bt disconnected
/org/freedesktop/NetworkManager/Devices/3 -- --
--
lo loopback unmanaged
/org/freedesktop/NetworkManager/Devices/2 -- --
--
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
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug yakkety
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1629620
Title:
DNS resolver stops accepting queries
Status in network-manager package in Ubuntu:
New
Bug description:
After a while / after resume from suspend, the system becomes unable
to respond to DNS queries, with the following output for example:
$ nslookup google.com 127.0.1.1
Server: 127.0.1.1
Address: 127.0.1.1#53
** server can't find google.com: REFUSED
This is on an up to date yakkety install. Changing resolv.conf to use
8.8.8.8, or restarting network-manager appears to fix this, at least until it
recurs again.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
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: GNOME
Date: Sat Oct 1 21:28:51 2016
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-08-21 (407 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
default via 192.168.1.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev docker0 scope link metric 1000 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric
600
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
docker0 bridge connected
/org/freedesktop/NetworkManager/Devices/1 docker0
63f0b05b-f699-4a68-81ce-f62d2c1a247d
/org/freedesktop/NetworkManager/ActiveConnection/0
wlp3s0 wifi connected
/org/freedesktop/NetworkManager/Devices/4 HOME-1622-5
6df3f2f0-fb86-43b5-802a-d59bc5734be3
/org/freedesktop/NetworkManager/ActiveConnection/2
24:DA:9B:B9:09:0E bt disconnected
/org/freedesktop/NetworkManager/Devices/3 -- --
--
lo loopback unmanaged
/org/freedesktop/NetworkManager/Devices/2 -- --
--
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/1629620/+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
