On Sun, Jul 09, 2023 at 02:10:02AM +0200, Petr Menšík wrote:
I think LLMNR should be disabled in whole distribution, because even
Microsoft is removing support for it [3]. I doubt it were wanted even in
Server builds especially. Those usually rely on more controlled
infrastructure, meaning standard unicast DNS.
I guess it can be disabled. It never gained any popularity.
I think mDNS has less
problematic implementation in avahi, but that has to be enabled explicitly.
I think that is desired especially on servers.
Actually, the coexistence of Avahi and system-resolved is an
interesting topic, underdocumented in my opinion. It would be nice
(but disabling LLMNR should not depend on) to have some FAQ on that.
- both avahi and resolved seem to have resolving capacity for mDNS
- only avahi can announce mDNS services (is this correct?)
- how do apps needing mDNS resolver work? Like CUPS. Do those apps talk
to avahi? To resolved? Are they using nss to resolve mDNS?
- how to those apps register resources (like printers) to announce? With
avahi? With resolved?
- should avahi be disabled when using resolved with MulticastDNS=true
(or =resolve)?
- what exactly MulticastDNS=true mean?
- which app should bind to port 5353/UDP
- etc.
--
Tomasz Torcz “Funeral in the morning, IDE hacking
tomek(a)pipebreaker.pl in the afternoon and evening.” - Alan Cox