Resolving such conflicts requires network-configuration changes that mDNS was designed to avoid.Īn mDNS message is a multicast UDP packet sent using the following addressing: local includes hosts that do not implement mDNS but that can be found via a conventional unicast DNS server.
Any host can relinquish its claim to a name by sending a response packet with a time to live (TTL) equal to zero.īy default, mDNS exclusively resolves hostnames ending with the. All machines in that subnet can then use that information to update their mDNS caches. That target machine then multicasts a message that includes its IP address.
When an mDNS client needs to resolve a hostname, it sends an IP multicast query message that asks the host having that name to identify itself. mDNS can work in conjunction with DNS Service Discovery (DNS-SD), a companion zero-configuration networking technique specified separately in RFC 6763. Although the Windows 10 implementation was limited to discovering networked printers, subsequent releases resolved hostnames as well. It uses IP multicast User Datagram Protocol (UDP) packets, and is implemented by the Apple Bonjour and open source Avahi software packages, included in most Linux distributions. Multicast DNS was first proposed by Bill Woodcock and Bill Manning in the IETF in 2000, and was eventually published as standards-track IETF RFC 6762 by Stuart Cheshire and Marc Krochmal thirteen years later. It was designed to work as either a stand-alone protocol or compatibly with standard DNS servers. It is a zero-configuration service, using essentially the same programming interfaces, packet formats and operating semantics as unicast Domain Name Service (DNS). In computer networking, the multicast DNS ( mDNS) protocol resolves hostnames to IP addresses within small networks that do not include a local name server.
0 kommentar(er)
