On Sat, Apr 2, 2022 at 5:22 PM Alexander Puchmayr <[email protected]> wrote: > > ## portage.local maps to 192.168.1.6 > ## DNS-Server provided via DHCP is 192.168.1.1 (openwrt-router) > > buildhost-desktop ~ # ping portage.local > ping: portage.local: Temporary failure in name resolution > > Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
So, I haven't really used resolved much, but I see you have mDNS enabled. Does the portage.local host broadcast itself using mDNS? If it is running Gentoo then the answer is no unless you have it running avahi, which is usually not installed by default. Many desktop-oriented linux distros provide avahi by default. A resolver that supports mDNS will not use DNS to resolve the .local TLD, in accordance with RFC 6762. If you intend to use .local for DNS and not mDNS then you probably do not want mDNS enabled. You can either disable it for resolved globally by setting MulticastDNS=no in the [Resolve] section of /etc/systemd/resolved.conf, or by disabling it for a specific network in your network manager (the setting has the same name for systemd-networkd). This is one of those reasons why it is best to not use the .local TLD for DNS on your home network. You can disable it on systemd-resolved, but some IoT device in your home might have it permanently enabled. It allows a form of name resolution to work without any DNS server as devices discover and broadcast on their own. -- Rich
