The problem seems to occur because the wireless network connects before my user logs in. If I do a reboot and login cycle with the wireless router turned off, when I turn it back on and the computer connects, /run/resolvconf/resolv.conf is updated correctly with the DNS nameserver information, as expected.
Note that whether or not DNS is working properly, systemd-resolve --status indicates that systemd-resolved has the correct information - it says "Current DNS Server: 10.1.1.1" - the problem is just that nobody updates the resolv.conf file unless a user is logged in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1819132 Title: DNS is broken after reboot or suspend Status in systemd package in Ubuntu: New Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-050000-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819132/+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
