Link-local multicast name resolution
| Link-local multicast name resolution | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Family: | Internet protocol family | ||||||||||||||||||||||||
| Operation area: | Name resolution | ||||||||||||||||||||||||
| Ports: | 5355 / UDP, 5355 / TCP | ||||||||||||||||||||||||
|
|||||||||||||||||||||||||
| Standards: | RFC 4795 | ||||||||||||||||||||||||
Link-Local Multicast Name Resolution ( LLMNR ) is a protocol based on the DNS -Paketformat, the IPv4 and IPv6 hosts , the name resolution allowed for hosts on the same local network. It is built into Windows Vista , Windows Server 2008 , Windows Server 2008 R2 , Windows 7 , Windows 8 and Windows 10 . LLMNR is also used on smartphones and tablets with the Microsoft Windows Phone and Windows 10 Mobile operating systems. Under Linux it is implemented in systemd-resolved. Under IPv4, LLMNR works in parallel with the name service NBNS integrated in NetBIOS and replaces NBNS under IPv6 , since NetBIOS does not support IPv6.
Protocol details
In order to answer inquiries, recipients listen on UDP port 5355 in the following multicast address ranges:
- IPv4 - 224.0.0.252, MAC address - 01-00-5E-00-00-FC
- IPv6 - FF02 :: 1: 3, Ethernet multicast address - 33-33-00-01-00-03
The recipients also listen on TCP port 5355 on the unicast address that the host uses to respond.
Similar to the mDNS , the LLMNR is based on the DNS protocol. There are A resource records for IPv4 addresses and AAAA resource records for IPv6 uses addresses. The probing takes place with the DNS type "ANY". In contrast to mDNS, name conflicts in the network are not handled. If a participant in the network finds that his name has already been taken, he remains silent and tries again after 15 minutes.
See also
credentials
Web links
- TechNet Link-Local Multicast Name Resolution
- RFC 4795 , Informational, Link-Local Multicast Name Resolution (LLMNR)
- MS-LLMNR profiles