Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

S. Cheshire
M. Krochmal

Stream:

IETF

Source:

NON WORKING GROUP

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6762

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6762

Abstract

As networked devices become smaller, more portable, and moreubiquitous, the ability to operate with less configuredinfrastructure is increasingly important. In particular, the abilityto look up DNS resource record data types (including, but not limitedto, host names) in the absence of a conventional managed DNS serveris useful.

Multicast DNS (mDNS) provides the ability to perform DNS-likeoperations on the local link in the absence of any conventionalUnicast DNS server. In addition, Multicast DNS designates a portion of the DNSnamespace to be free for local use, without the need to pay anyannual fee, and without the need to set up delegations or otherwiseconfigure a conventional DNS server to answer for those names.

The primary benefits of Multicast DNS names are that (i) they require littleor no administration or configuration to set them up, (ii) they workwhen no infrastructure is present, and (iii) they work duringinfrastructure failures.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.