Compare commits

...

4 Commits

Author SHA1 Message Date
Petr Menšík bf429a1ec5
Merge 1fcb30098f into 7a9d0abe4d 2024-11-26 16:21:00 +05:30
Luca Boccassi 7a9d0abe4d Revert "man: use MIT-0 license for example codes in daemon(7)"
This reverts commit 6046cc3660.
2024-11-26 19:47:21 +09:00
Yu Watanabe 6046cc3660 man: use MIT-0 license for example codes in daemon(7)
This page contains many short example codes. I do not think we should
add SPDX-License-Identifier for all codes.

Closes #35356.
2024-11-26 11:12:08 +01:00
Petr Menšík 1fcb30098f Disable LLMNR protocol in default builds
Even Microsoft has disabled resolution over LLMNR protocol in their
Windows 10. I have found that when testing something and wondered, why
mDNS works but LLMNR does not on Windows machine in our network. Found
mDNS is now preferred and updated systems get it disabled.

Found an article about that is by design, not conincidental:
https://techcommunity.microsoft.com/t5/networking-blog/aligning-on-mdns-ramping-down-netbios-name-resolution-and-llmnr/ba-p/3290816

Because the way systemd-resolved is breaking some operations in DNS, I
would like it disabled by default. Multicast DNS is preferred solution
and has separate .local domain. It makes it easier to decide which
queries should be directed to multicast resolution. Legacy users on
Windows 7 should be forced to enable it, if they want to use it.

Related: #23622
2023-07-05 21:48:38 +02:00
1 changed files with 1 additions and 1 deletions

View File

@ -360,7 +360,7 @@ option('default-mdns', type : 'combo',
option('default-llmnr', type : 'combo',
choices : ['yes', 'resolve', 'no'],
description : 'default LLMNR mode',
value : 'yes')
value : 'no')
option('dns-over-tls', type : 'combo', choices : ['auto', 'gnutls', 'openssl', 'true', 'false'],
description : 'DNS-over-TLS support')
option('dns-servers', type : 'string',