[GH-ISSUE #322] Support Link-Local Multicast Name Resolution (LLMNR) #150

New issue

Open

opened 2026-03-07 22:28:30 +03:00 by kerem · 0 comments

kerem commented

2026-03-07 22:28:30 +03:00

Owner

Originally created by @briansmith on GitHub (Jan 1, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/322

From Wikipedia's Link-Local Multicast Name Resolution article:

It is included in Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 10. It is also implemented by systemd-resolved on Linux.[2] LLMNR is defined in RFC 4795.

Conversely, Multicast DNS (mDNS) is supported by macOS and other platforms. mDNS is clearly the future, and recent updates to Windows 10 have started enabling mDNS for some specific features, e.g. printer discovery. I personally would prioritize mDNS higher than LLMNR and I suggest providing a way to enable mDNS without enabling LLMNR. However, I think some users will find LLMNR helpful.

From Wikipedia's Zero-configuration networking:

The mDNS and LLMNR protocols have minor differences in their approach to name resolution. mDNS allows a network device to choose a domain name in the local DNS namespace and announce it using a special multicast IP address. This introduces special semantics for the domain local,[11] which is considered a problem by some members of the IETF.[12] The current LLMNR draft allows a network device to choose any domain name, which is considered a security risk by some members of the IETF.[13] mDNS is compatible with DNS-SD as described in the next section, while LLMNR is not.[14].

Originally created by @briansmith on GitHub (Jan 1, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/322 From [Wikipedia's Link-Local Multicast Name Resolution](https://en.wikipedia.org/wiki/Link-Local_Multicast_Name_Resolution) article: > It is included in Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 10. It is also implemented by systemd-resolved on Linux.[2] LLMNR is defined in RFC 4795. Conversely, Multicast DNS (mDNS) is supported by macOS and other platforms. mDNS is clearly the future, and recent updates to Windows 10 have started enabling mDNS for some specific features, e.g. printer discovery. I personally would prioritize mDNS higher than LLMNR and I suggest providing a way to enable mDNS without enabling LLMNR. However, I think some users will find LLMNR helpful. From [Wikipedia's Zero-configuration networking](https://en.wikipedia.org/wiki/Zero-configuration_networking#Name_service_discovery): > The mDNS and LLMNR protocols have minor differences in their approach to name resolution. mDNS allows a network device to choose a domain name in the local DNS namespace and announce it using a special multicast IP address. This introduces special semantics for the domain local,[11] which is considered a problem by some members of the IETF.[12] The current LLMNR draft allows a network device to choose any domain name, which is considered a security risk by some members of the IETF.[13] mDNS is compatible with DNS-SD as described in the next section, while LLMNR is not.[14].