RFC 4702: The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option
In plain English — editorial summary, not part of the RFC
This document describes a Dynamic Host Configuration Protocol for IPv4 (DHCPv4) option that can be used to exchange information about a DHCPv4 client's fully qualified domain name and about responsibility for updating the DNS RR related to the client's address assignment. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4702
- Published
- October 2006
- Authors
- M. Stapp; B. Volz; Y. Rekhter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4704The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) OptionCurrent
October 2006
- RFC 4388Dynamic Host Configuration Protocol (DHCP) LeasequeryUpdated
February 2006
- RFC 3527Link Selection sub-option for the Relay Agent Information Option for DHCPv4Current
April 2003
- RFC 3396Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)Current
November 2002
- RFC 2131Dynamic Host Configuration ProtocolUpdated
March 1997
- RFC 7839Access-Network-Identifier Option in DHCPCurrent
June 2016
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 7969Customizing DHCP Configuration on the Basis of Network TopologyCurrent
October 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?