host's fqdn not resolving

[Chris Green]

On Sat, Aug 20, 2022 at 05:41:12PM -0600, Stuart McGraw wrote:
[snip description of problem]
> 
> Surely with systemd-resolved, avahi, mdns, nsswitch,conf, /etc/hosts
> and probably a half dozen other pieces involved, there must be some
> magical configuration change that can achieve this?
> 
> I have tried (really just stabs in the dark) setting:
>   /etc/systemd/resolved.conf: Domains=home
> and:
>  /etc/avahi/avahi-daemon.conf: domain-name=home
> but neither had the desired effect.
> 
The default set-up using systemd, avahi and so on is a *mess*.  It's
possibly OK until you have a large[ish] LAN with a lot of systems on it.

I simply disable systemd-resolved, remove avahi and run dnsmasq on one
of my systems, everything then works as expected and you don't have to
use (unnecessary) .local or .home suffixes on names.  You can simply
use the name of each system to refer to it, or the FQDN if you have
a domain name for the LAN.

-- 
Chris Green