I have encountered this bug as well. I have raised it with systemd-resolved. The internal resolver of systemd does not properly search the local dns. Only fqdn's will resolve. This is easily mitigated and does not require a whole bunch of enabling or disabling of things.
The DHCP process will almost always provide a valid DNS locally and the DHCP client in systemd does actually create a valid resolve.conf. You just have to point /etc/resolv.conf to it. At the time of writing the systemd people refuse to accept that this is a bug. They continue to refer to it as a documentation issue. I honestly don't believe they are testing it. # Just making sure I'm out of the / dir cd /etc # resolv.conf is a link to ../run/systemd/resolve/stub-resolv.conf Which directs thing to use the local resolved. So I nuke it. sudo rm resolve.conf # Then I go and use the actual resolv.conf that actually works. sudo ln -s ../run/systemd/resolve/resolv.conf resolv.conf The above workaround is good. It will allow you to take your laptop onto all different types of networks. It will work correctly. This is for at least systemd version 237 and above. I haven't checked to see if 236 has the proper file generated or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Hotel Hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
