> Isn't that what the RFC 6762 recommends? It is required (MUST). The optional thing the RFC states after this requirement:
Implementers MAY choose to look up such names concurrently via other mechanisms (e.g., Unicast DNS) and coalesce the results in some fashion. This is why I asked about whether a parallel lookup is possible; which would be according to the standard and would work for the particular use case of networks that have ".local" in use for unicast DNS. Unfortunately that doesn't work with nsswitch, if I understand Petr correctly. Esko -----Original Message----- From: avahi <avahi-boun...@lists.freedesktop.org> On Behalf Of Éric Bischoff Sent: Friday, December 9, 2022 08:29 To: Avahi ML <avahi@lists.freedesktop.org> Subject: Re: [avahi] Is it time to drop .local SOA heuristic? Le mercredi 7 décembre 2022, 17:37:33 CET Petr Menšík a écrit : > (...) > An alternative would be removing this test at all and do mdns queries > always. Isn't that what the RFC 6762 recommends? https://www.ietf.org/rfc/rfc6762.txt Any DNS query for a name ending with ".local." MUST be sent to the mDNS IPv4 link-local multicast address 224.0.0.251 (or its IPv6 equivalent FF02::FB). Hoping not to misunderstand something and that it helps, -- Éric Bischoff
