TL;DR add this config to dnsmasq.conf to expand your LAN single-label hosts into FQDNs that systemd won’t hate:


For decades, DNS resolution was fine, and then systemd arrived and it was not. For the past couple years, for me and many others, systemd-resolved has been quite a headache, failing basic DNS resolution on any fresh Ubuntu (and other) installs. A real joy when you just want to get things going ASAP. After years of getting around it with shitty hacks, I finally nailed down what was going on.

Poettering and his crew decided that “single-label” host names on your LAN should never be allowed to resolve, even though it always used to in what he calls “classic DNS”. The systemd-resolved DNS handler in a vanilla install of Ubuntu 20.04 will drop your name resolution requests simply because the name does not have a dot in it. End of story. How nice. This awful default behavior follows some 2013 guidelines that were never previously enforced, at least not on me.

I use the simplest possible solutions that work, and for me that is dnsmasq. You can use one config file to configure static IPs for the MACs of all your LAN boxes. I just needed to reconfigure it to expand single-label names into longer “fake” FQDNs, with some dnsmasq hackery, and DNS on new boxes now works out of the gate. See the top of post (or this SO answer) for the configuration details.

There are supposed to be other solutions, like flipping on the LLMNR flag of systemd-resolved. That didn’t work for me, and I don’t want to have to futz with every single new LAN box and VM anyway. Hopefully this nightmare is behind me now. I hope for you, as well.

One Comment

  1. […] default to vanilla systemd-resolved DNS resolution. It’s all possible and works elegantly, with a few tweaks to […]

Leave a Reply