This article may require cleanup to meet Wikipedia's quality standards. (December 2010) (Learn how and when to remove this template message)
Zero-configuration networking (zeroconf) is a set of technologies that automatically creates a usable computer network based on the Internet Protocol Suite (TCP/IP) when computers or network peripherals are interconnected. It does not require manual operator intervention or special configuration servers. Without zeroconf, a network administrator must set up network services, such as Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS), or configure each computer's network settings manually.
Zeroconf is built on three core technologies: automatic assignment of numeric network addresses for networked devices, automatic distribution and resolution of computer hostnames, and automatic location of network services, such as printing devices.
|Internet protocol suite|
- 1 Background
- 2 Address selection
- 3 Name service discovery
- 4 Service discovery
- 5 Standardization
- 6 Security issues
- 7 Major implementations
- 8 See also
- 9 References
- 10 External links
Computer networks use numerical network addresses to identify communications endpoints in a network of participating devices. This is similar to the telephone network which assigns a string of digits to identify each telephone. In modern networking protocols, information to be transmitted is divided into a series of network packets. Every packet contains the source and destination addresses for the transmission. Network routers examine these addresses to determine the best network path in forwarding the data packet at each step toward its destination.
Similarly to telephones being labeled with their telephone number, it was a common practice in early networks to attach an address label to networked devices. The dynamic nature of modern networks, especially residential networks in which devices are powered up only when needed, desire dynamic address assignment mechanisms that do not require user involvement for initialization and management. These systems automatically give themselves common names chosen either by the equipment manufacturer, such as a brand and model number, or chosen by users for identifying their equipment. The names and addresses are then automatically entered into a directory service.
Early computer networking was built upon technologies of the telecommunications networks and thus protocols tended to fall into two groups: those intended to connect local devices into a local area network (LAN), and those intended primarily for long-distance communications. The latter wide area network (WAN) systems tended to have centralized setup, where network administrator would manually assign addresses and names. LAN systems tended to provide more automation of these tasks, so that new equipment could be added to a LAN with a minimum of operator and administrator intervention.
An early example of a zero-configuration LAN system is AppleTalk, a protocol introduced by Apple Inc. for the early Macintosh computers in the 1980s. Macs, as well as other devices supporting the protocol, could be added to the network by simply plugging them in; all further configuration was automated. Network addresses were automatically selected by each device using a protocol known as AppleTalk Address Resolution Protocol (AARP), while each machine built its own local directory service using a protocol known as Name Binding Protocol (NBP). NBP included not only a name, but the type of device and any additional user-provided information such as its physical location or availability. Users could look up any device on the network with the application Chooser, which filtered names based on the device type.
On Internet Protocol networks, the Domain Name System database for a network was initially maintained manually by a network administrator. Efforts to automate maintenance of this database, led to the introduction of a number of new protocols providing automated services, such as the Dynamic Host Configuration Protocol (DHCP).
Hosts on a network must be assigned IP addresses that uniquely identify them to other devices on the same network. On some networks there is a central authority that assigns these addresses as new devices are added. Mechanisms were introduced to handle this task automatically, and both IPv4 and IPv6 now include systems for address autoconfiguration, which allows a device to determine a safe address to use through simple mechanisms. For link-local addressing, IPv4 uses the special block 169.254.0.0/16 as described in RFC 3927 while IPv6 hosts use the prefix fe80::/10. More commonly addresses are assigned by a DHCP server, often built into common networking hardware like computer hosts or routers.
Most IPv4 hosts use link-local addressing only as a last resort when a DHCP server is unavailable. An IPv4 host otherwise uses its DHCP-assigned address for all communications, global or link-local. One reason is that IPv4 hosts are not required to support multiple addresses per interface, although many do. Another is that not every IPv4 host implements distributed name resolution (e.g., multicast DNS), so discovering the autoconfigured link-local address of another host on the network can be difficult. However, discovering the DHCP-assigned address of another host also requires either distributed name resolution or a unicast DNS server with this information, and some networks feature DNS servers that are automatically updated with DHCP-assigned host and address information.
IPv6 hosts are required to support multiple addresses per interface; moreover, every IPv6 host is required to configure a link-local address even when global addresses are available. IPv6 hosts may additionally self-configure additional addresses on receipt of router advertisement messages, thus eliminating the need for a DHCP server.
Both IPv4 and IPv6 hosts may randomly generate the host-specific part of an autoconfigured address. IPv6 hosts generally combine a prefix of up to 64 bits with a 64-bit EUI-64 derived from the factory-assigned 48-bit IEEE MAC address. The MAC address has the advantage of being globally unique, a property inherited by the EUI-64. The IPV6 protocol stack includes duplicate address detection to avoid conflicts with other hosts. In IPv4, the method is called link-local address autoconfiguration. However, Microsoft refers to this as Automatic Private IP Addressing (APIPA) or Internet Protocol Automatic Configuration (IPAC) (supported since at least Windows 98).
Name service discovery
Internet protocols use IP addresses for communications, but these are not really human-readable; IPv6 in particular uses very long strings of digits that are not easily entered manually. To address this issue, the internet has long used the Domain Name System (DNS), which allows human-readable names to be associated with IP addresses, and includes code for looking up these names from a hierarchical database system. Users type in domain names, such as example.org, which the computer's DNS software looks up in the DNS databases to retrieve an IP address, and then hands off that address to the networking software for further communications.
Looking up a DNS address requires the IP address of the DNS server to be known. This has normally been accomplished by typing in the address of a known server into a field in one of the devices on the network. In early systems this was normally required on every device, but this has been pushed up one layer in the hierarchy to the DHCP servers or wide-area network devices like cable modems that receive this information from their IP provider. This has reduced the user-side administration load and provides a key element of zero-configuration access.
DNS was intended to provide uniform names to groups of devices within the same administration realm, such as example.org, provided by a name service. Assigning an address to a local device, e.g., thirdfloorprinter.example.org, normally requires administrator access to the DNS server and is often accomplished manually. Additionally, traditional DNS servers are not expected to automatically correct for changes in configuration. For instance, if a printer is moved from one floor to another it might be assigned a new IP address by the local DHCP server.
To address the need for automatic configuration, Microsoft implemented NetBIOS Name Service part of which is the Computer Browser Service already in Microsoft Windows for Workgroups 3.11 as early as 1992. NetBIOS Name Service is zero-configuration on networks with a single subnet and may be used in conjunction with a WINS server or a (Microsoft) DNS server that supports (secure) automatic registration of addresses to have a management overhead that is small but not zero even on very large (enterprise) networks. The protocols NetBIOS can use are part of the SMB suite of open protocols which are implemented on Linux and iOS, although Windows typically supports a wider range of so-called dialects which can be negotiated between (Windows) clients that support it. For example, Computer Browser Services running on server operating systems or later versions of Windows are elected as so-called master browser over those that are not running a server operating system or run older versions of Windows.
In 2000, Bill Manning and Bill Woodcock described the Multicast Domain Name Service which spawned the implementations by Apple and Microsoft. Both implementations are very similar. Apple's Multicast DNS (mDNS) is published as a standards track proposal (RFC 6762), while Microsoft's Link-local Multicast Name Resolution (LLMNR) is published as informational RFC 4795. LLMNR is included in every Windows version from Windows Vista onwards and acts as a side-by-side alternative for Microsoft's NetBIOS Name Service over IPv4 and as a replacement over IPv6, since NetBIOS is not available over IPv6. Apple's implementation is available as the Bonjour Service, previously Rendezvous, since 2002 in Mac OS X v10.2. The Bonjour implementation (mDNSResponder) is available under the Apache 2 Open Source License and is included in Android 4.1 "Jelly Bean" and later under the same license.
Use of either NetBIOS or LLMNR services on Windows is essentially automatic, since using standard DNS client API's will result in the use of either NetBIOS or LLMNR depending on what name is being resolved (whether the name is a local name or not), the network configuration in effect (e.g. DNS suffixes in effect) and (in corporate networks) the policies in effect (whether LLMNR or NetBIOS are disabled), although developers may opt into bypassing these services for individual address lookups.
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, which is considered a problem by some members of the IETF. 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. mDNS is compatible with DNS-SD as described in the next section, while LLMNR is not.
Name services such as mDNS, LLMNR and others do not provide information about the type of device or its status. A user looking for a nearby printer, for instance, might be hindered if the printer was given the name "Bob". Service discovery provides additional information about devices. Service discovery is sometimes combined with a name service, as in Apple's Name Binding Protocol and Microsoft's NetBIOS (including SMB as supported on non-Microsoft operating systems).
NetBIOS Service Discovery
NetBIOS on Windows and its sibling SMB on other operating systems, supports individual hosts on the network to advertise services, such as file shares and printers. It also supports for example a network printer to advertise itself as a host sharing a printer device and any related services it supports. Depending on how a device is attached (to the network directly, or to the host which shares it) and which protocols are supported however, Windows clients connecting to it may prefer to use SSDP or WSD over using NetBIOS. NetBIOS is one of the providers on Windows implementing the more general discovery process dubbed 'Function Discovery' which includes built-in providers for PnP, Registry, NetBIOS, SSDP and WSD of which the former two are local-only and the latter three support discovery of networked devices. None of these need any configuration for use on the local subnet. NetBIOS has traditionally been supported only in expensive printers for use in companies and the cheapest devices of some brands today still don't have support for it, but home and SOHO users would connect printers to a computer over say a parallel port or USB and share it from the computer. However, today even entry-level printers with Wi-Fi or Ethernet support of some brands support it natively, allowing the printer to be used without configuration even on very old operating systems (combined with a generic PostScript driver, for example).
Web Services Dynamic Discovery (WS-Discovery) is a technical specification that defines a multicast discovery protocol to locate services on a local network. It operates over TCP and UDP port 3702 and uses IP multicast address 18.104.22.168. As the name suggests, the actual communication between nodes is done using web services standards, notably SOAP over UDP. Windows supports it in the form of WSD and WPDS and many device and appliance manufacturers support it, such as HP and Brother printers.
DNS-based service discovery
DNS-SD allows clients to discover a named list of service instances, given a service type, and to resolve those services to hostnames using standard DNS queries. The specification is compatible with existing unicast DNS server and client software, but works equally well with Multicast DNS in a zero-configuration environment. Each service instance is described using a DNS SRV (RFC 2782) and DNS TXT (RFC 1035) record. A client discovers the list of available instances for a given service type by querying the DNS PTR (RFC 1035) record of that service type's name; the server returns zero or more names of the form "<Service>.<Domain>", each corresponding to a SRV/TXT record pair. The SRV record resolves to the domain name providing the instance, while the TXT can contain service-specific configuration parameter. A client can then resolve the A/AAAA record for the domain name and connect to the service.
In 1997 Stuart Cheshire proposed[self-published source?] adapting Apple's mature Name Binding Protocol to IP networks to address the lack of service discovery capability. Cheshire subsequently joined Apple and authored IETF draft proposals for Multicast DNS and DNS-based Service Discovery, supporting the transition from AppleTalk to IP networking. In 2002, Apple announced an implementation of both protocols under the name Rendezvous (later renamed Bonjour), included in Mac OS X 10.2 and replacing the Service Location Protocol used in 10.1. In 2013, the proposals were ratified as RFC 6762 and RFC 6763.
DNS-SD with multicast
Multicast DNS (mDNS) is a protocol that uses packets similar to unicast DNS except sent over a multicast link to resolve hostnames. Each host listens on the mDNS port, 5353, and resolves requests for the DNS record of its .local hostname (e.g. the A, AAAA, CNAME) to its IP address. When an mDNS client needs to resolve a local hostname to an IP address, it sends a DNS request for that name to a well-known multicast address; the computer with the corresponding A/AAAA record replies with its IP address. The mDNS multicast address is 22.214.171.124 for IPv4 and ff02::fb for IPv6 link-local addressing.
DNS service discovery (DNS-SD) requests can also be sent over a multicast link, and it can be combined with mDNS to yield zero-configuration DNS-SD. It still uses DNS PTR, SRV, TXT records to advertise instances of service types, domain names for those instances, and optional configuration parameters for connecting to those instances. But SRV records can now resolve to multicastable .local domain names, which mDNS can resolve to local IP addresses.
UPnP has some protocol variants with the purpose of service discovery.
Simple Service Discovery Protocol (SSDP) is a UPnP protocol, used in Windows XP and later. SSDP uses HTTP notification announcements that give a service-type URI and a Unique Service Name (USN). Service types are regulated by the Universal Plug and Play Steering Committee. SSDP is supported by many printer, NAS and appliance manufacturers such as Brother, certain brands of network equipment, and in many SOHO firewall appliances, where host computers behind it may pierce holes for applications. It is also used in home theater PC systems, where media exchange between host computers and the media center is facilitated using SSDP.
DLNA is another suite of standards that uses UPnP for its discovery of networked devices, which has a long list of manufacturers producing devices that support it, such as TVs from most if not all large brands, NAS devices and so forth. As such, it is also supported by all major operating systems.
Efforts toward an IETF standard protocol
Service Location Protocol (SLP) is supported by Hewlett-Packard's network printers, Novell, and Sun Microsystems. SLP is described in RFC 2608 and RFC 3224 and implementations are available for both Solaris and Linux.
AllJoyn is an open source software stack for a myriad of devices, ranging from the tiniest IoT devices to the largest computers, for discovery and control of devices on networks (Wifi, Ethernet) and other links (Bluetooth, ZigBee, etc.). It uses (amongst others) mDNS and HTTP over UDP.
Following the failure of LLMNR to become an Internet standard, Apple was asked by the IETF to submit the mDNS/DNS-SD specs for publication as informational RFC as well, given that mDNS/DNS-SD is used much more widely than LLMNR.. In February 2013 mDNS and DNS-SD were published as Standards Track Proposals RFC 6762 and RFC 6763.
Because mDNS operates under a different trust model than unicast DNS—trusting the entire network rather than a designated DNS server, it is vulnerable to spoofing attacks by any system within the multicast IP range. Like SNMP and many other network management protocols, it can also be used by attackers to quickly gain detailed knowledge of the network and its machines. Because of this, applications should still authenticate and encrypt traffic to remote hosts (e.g. via RSA, SSH, etc.) after discovering and resolving them through DNS-SD/mDNS.
Bonjour (formerly known as Rendezvous) from Apple Inc., uses mDNS and DNS Service Discovery. Apple changed its preferred zeroconf technology from SLP to mDNS and DNS-SD between Mac OS X 10.1 and 10.2, though SLP continues to be supported by Mac OS X.
Apple's mDNSResponder has interfaces for C and Java and is available on BSD, Apple Mac OS X, Linux, other POSIX based operating systems and MS Windows. The Windows downloads are available from Apple's website.
Avahi is a Zeroconf implementation for Linux and BSDs. It implements IPv4LL, mDNS and DNS-SD. It is part of most Linux distributions, and is installed by default on some. If run in conjunction with nss-mdns it also offers host name resolution.
Avahi also implements binary compatibility libraries that emulate Bonjour and the historical mDNS implementation Howl, so software made to use those implementations can also utilize Avahi through the emulation interfaces.
MS Windows CE 5.0
Link-local IPv4 addresses
There are some link-local IPv4 address implementations available:
- Apple Mac OS and MS Windows have supported link-local addresses since 1998. Apple released its open-source implementation in the Darwin bootp package.
- Avahi contains an implementation of IPv4LL in the avahi-autoipd tool.
- Zero-Conf IP (zcip).
- BusyBox can embed a simple IPv4LL implementation.
- Stablebox, a fork from Busybox, offers a slightly modified IPv4LL implementation named llad.
- Zeroconf, a package based on Simple IPv4LL, a shorter implementation by Arthur van Hoff.
The above implementations are all stand-alone daemons or plugins for DHCP clients that only deal with link-local IP addresses. Another approach is to include support in new or existing DHCP clients:
- Elvis Pfützenreuter has written a patch for the uDHCP client/server.
- dhcpcd is an opensource DHCP client for Linux and BSD that includes IPv4LL support. It is included as standard in NetBSD.
- RFC 4862. IETF. doi:10.17487/RFC4862. https://tools.ietf.org/html/rfc4862.
- RFC 3927. IETF. doi:10.17487/RFC3927. https://tools.ietf.org/html/rfc3927.
- "Apipa", MS Developer Network, Microsoft
- "How to use automatic TCP/IP addressing without a DHCP server", Knowledge base, Microsoft
- Marshall Brain and Stephanie Crawford, "How Domain Name Servers Work", howstuffworks
- "Description of the Microsoft Computer Browser Service". Microsoft Knowledge Base. Microsoft. Retrieved 1 November 2015.
- Manning, Multicast Domain Name Service (draft), Water springs
- Microsoft TechNet Library Link-Local Multicast Name Resolution (webpage), Microsoft
- Bonjour Licensing and Trademarks (webpage), Apple
- Android 4.1 APIs (webpage), Google
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard (electronic mail message), IETF
- Re: Summary of the LLMNR Last Call (electronic mail message), IETF
- Summary of the LLMNR Last Call (electronic mail message), IETF
- More details on the differences (electronic mail message), IETF
- "About Function Discovery". Windows Dev Center. Microsoft. Retrieved 1 November 2015.
- Cheshire, Stuart, Name Binding Protocol over IP (rant)
- Zero conf
- "RFC 6762 Document History". IETF.
- "RFC 6763 Document History". IETF.
- RFC 6763. IETF. doi:10.17487/RFC6763. https://tools.ietf.org/html/rfc6763.
- "Ubuntu 15.10 desktop manifest". Ubuntu. Retrieved 23 October 2015.
- "Windows.Networking.ServiceDiscovery.Dnssd namespace". Windows Dev Center. Microsoft. Retrieved 1 November 2015.
- Service types, DNS-SD
- Zero Configuration Networking (zeroconf) Charter, IETF
- DNS Extensions (dnsext) Charter, IETF
- Service Location Protocol (svrloc) Charter, IETF
- Name (MDNS) Poisoning Attacks Inside the LAN (World Wide Web log), GNU citizen
- A Rendezvous with Java, Mac Dev Center, 2004-08-31
- "Bonjour for MS Windows 1.0.4", Support, Apple
- Lennart, nss-mdns 0.10, DE: 0 pointer
- zcip, Source forge
- "Stable box", Code, Google
- Zeroconf, AU: UTS
- AVH IPv4LL (C source code), Zero conf
- "Zeroconf in udhcpc", udhcpc (electronic mail message), Busy box, May 2005
- Marples, Roy, dhcpcd (wiki) (project)
- "Link-Local ARP Measurements", AIR (wiki), NE: UVA
- JmDNS, Source forge, a pure Java implementation of mDNS/DNS-SD.
- pyZeroConf, Source forge, a pure Python implementation of mDNS/DNS-SD.
- Mono.Zeroconf, Mono project, a cross platform (Linux, MS Windows, Apple Mac), unified Mono/.NET library for Zeroconf, supporting both Bonjour and Avahi.
- WxServDisc, Source forge, a cross-platform wxWidgets-based service discovery module without external dependencies.
- Cheshire, Stuart, Specification (draft), Multicast DNS.
- ———, DNS-Based Service Discovery Specification (draft), DNS‐SD.
- ———, Zeroconf (video) (tech talk), Google.
- ———, Zeroconf, including Internet drafts.
- DNS-SD, DNS based Service Discovery
- Multicast DNS.
- Johns, Heath (December 2002), Understanding Zeroconf and Multicast DNS (article), O'Reilly, slightly outdated.
- "Zeroconf Technologies", AIR (wiki), NL: UVA.
- DNSEXT working group (charter), IETF, which coordinates LLMNR standardization.
- Service Location Protocol, version 2. doi:10.17487/RFC2608. RFC 2608. https://tools.ietf.org/html/rfc2608.
- Steinberg, Daniel; Cheshire, Stuart, Zero Configuration Networking: The Definitive Guide, O'Reilly.