Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4701
Discuss this RFC: Send questions or comments to the mailing listdnsext@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4701
It is possible for Dynamic Host Configuration Protocol (DHCP) clientsto attempt to update the same DNS Fully Qualified Domain Name (FQDN)or to update a DNS FQDN that has been added to the DNS for anotherpurpose as they obtain DHCP leases. Whether the DHCP server or theclients themselves perform the DNS updates, conflicts can arise. Toresolve such conflicts, RFC 4703 proposes storing client identifiersin the DNS to unambiguously associate domain names with the DHCPclients to which they refer. This memo defines a distinct ResourceRecord (RR) type for this purpose for use by DHCP clients and servers:the "DHCID" RR. [STANDARDS-TRACK]
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.