This is a dup of #1639776
A patched deb package is here:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/comments/7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629620
Title:
DNS r
*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241
** This bug has been marked a duplicate of bug 1631241
Name resolution stops working after resume from suspend
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug is no longer a duplicate of bug 1631241
Name resolution stops working after resume from suspend
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out afte
When the network interface providing dns is managed by network manager,
dns fails on relaunch of the interface
test dns:
dig x$(date +%N).blogspot.com +short
if it fails, there is no output
verify that Internet is available:
dig @8.8.8.8 x$(date +%N).blogspot.com +short
blogspot.l.googleuserconte
dns appears to be ok, it's just not working
for example, one can do:
nmcli d show | grep DNS
IP4.DNS[1]: 192.168.1.15
the Network Manager-provided dnsmasq is just not using that dns server
that network manager knows about.
--
You received this bug notification because
https://bugzilla.gnome.org/show_bug.cgi?id=774337
** Bug watch added: GNOME Bug Tracker #774337
https://bugzilla.gnome.org/show_bug.cgi?id=774337
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16296
this seems to be less of a problem after switching /etc/resolv.conf to
point to the systemd-resolved managed file instead of the resolvconf
managed file. not sure exactly which package should be changed to have
this work automatically?
--
You received this bug notification because you are a memb
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629620
Tit
I noticed this issue on one of the two computers I upgraded from xenial
to yakkety. Specifically the affected computer was an 2016 Dell XPS 13.
They're both similarly configured ubuntu installations with Broadcom
nics, so it's curious that this only affects one of them. I'm not sure
what debug inf
