I'm noticing the same behavior. For a while I see DNS requests from the build in dnsmasq being sent to the forwarding DNS servers (either as set by DHCP or manually in the network manager config) and responses coming in just fine. After a while however I only see the request packets being sent on my ethernet interface, but no response packets being received on my network interface (as shown by wireshark).
However it does look like disabling the build-in dnsmasq in network manager fixes the problems for now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589005 Title: After update DNS work unstable Status in network-manager package in Ubuntu: Confirmed Bug description: Today I have updated network-manager from update repo and chrome have started get err_name_resolution_failed apt started get network errors. W: Failed to fetch http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb Temporary failure resolving 'by.archive.ubuntu.com' I got same error when previously update network-manager from ubuntu- proposed, so I think this packet with regression moved to normal update. workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and install it using sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb and lock version echo "network-manager hold" | sudo dpkg --set-selections "apt update" going to show network-manager as upgradable but "apt upgrage" going to ignore it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 4 01:39:17 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-01 (33 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.100.1 dev enp8s0 proto static metric 100 169.254.0.0/16 dev enp8s0 scope link metric 1000 192.168.100.0/24 dev enp8s0 proto kernel scope link src 192.168.100.9 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Проводное соединение 1 34318290-4c71-4b1f-9154-d0f134b91440 802-3-ethernet 1464993435 Sat 04 Jun 2016 01:37:15 MSK yes 4294966297 no /org/freedesktop/NetworkManager/Settings/2 yes enp8s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 HUAWEI-KpW2 1 8087b7e0-51dc-43c4-8928-4d03c85a5762 802-11-wireless 1464546384 Sun 29 May 2016 21:26:24 MSK yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp8s0 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Проводное соединение 1 34318290-4c71-4b1f-9154-d0f134b91440 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp9s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
