[Bug 1642973] [NEW] DNS stops working when changing networks

[gpothier]

Public bug reported:

Since upgrading to 16.10 I am having frequent DNS failures. It usually happens when I change networks and after resume from suspend, for example going to home from work, or vice versa. When this happens, connectivity is fine (I can ping 8.8.8.8 for instance), but I cannot resolve names (eg. google.com).
Restarting network-manager instantaneously fixes the issue.

Curiously I have not found this bug on Launchpad. Here is some related
stuff I've seen:

https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1640286
(as described, it seems specific to Chrome)

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721
(DNS resolution issues with VPNs, but it looks like it has been solved; at least I am not affected anymore)

http://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns
(forum post that describes a similar issue, but again for VPNs)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: resolvconf 1.79ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Nov 18 11:07:53 2016
InstallationDate: Installed on 2015-01-23 (664 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: resolvconf
UpgradeStatus: Upgraded to yakkety on 2016-10-30 (19 days ago)

** Affects: resolvconf (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1642973

Title:
  DNS stops working when changing networks

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Since upgrading to 16.10 I am having frequent DNS failures. It usually happens when I change networks and after resume from suspend, for example going to home from work, or vice versa. When this happens, connectivity is fine (I can ping 8.8.8.8 for instance), but I cannot resolve names (eg. google.com).
  Restarting network-manager instantaneously fixes the issue.

  Curiously I have not found this bug on Launchpad. Here is some related
  stuff I've seen:

  https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1640286
  (as described, it seems specific to Chrome)

  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721
  (DNS resolution issues with VPNs, but it looks like it has been solved; at least I am not affected anymore)

  http://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns
  (forum post that describes a similar issue, but again for VPNs)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: resolvconf 1.79ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 18 11:07:53 2016
  InstallationDate: Installed on 2015-01-23 (664 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to yakkety on 2016-10-30 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1642973/+subscriptions