Visual RFC.
ALL RFCs / RFC 2131
Read the RFC ↗
RFC 2131 / MECHANISMS

Request settings without a lease

06

A device with an externally configured IPv4 address can request other configuration using DHCPINFORM.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 2131 · § 4.4.3EXAMPLE
3 / 3
Request settings without a leaseAn externally assigned address stays fixed while DHCPINFORM obtains options without a new lease.static clientExisting IP: 192.0.2.40DHCPINFORMrequest router / DNS settingsDHCPACK optionsrouterDNSno leaseConfiguration response, not address allocation
03
Apply the returned configuration.

The response supplies parameters without assigning an address or lease.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 1541RFC 2131 § 1.1

RFC 2131 adds DHCPINFORM for parameter-only configuration and removes the former minimum lease-time restriction.

Read the updated RFC section ↗
KEY POINT

Ask for settings without allocating another address.

  • DHCPINFORM can carry a parameter-request list.
  • The server returns DHCPACK with configuration options but does not allocate an address or provide lease timing.
  • DHCP’s base protocol is not authenticated; rogue servers can supply misleading network configuration.
DETAILS

Options such as routers and DNS servers are defined in RFC 2132. Do not confuse DHCPINFORM with address allocation or lease renewal.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Discover and select an address
  2. Reach a server through a relay
  3. Renew before the lease expires
  4. Validate a remembered address
  5. Check conflicts and release addresses
  6. Request settings without a lease
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗