DHCP: Discover, Offer, Request and Acknowledge
DHCPv4 lets a host obtain an address lease and other network configuration from a server. The messages explain how a client selects and renews a configuration; they do not authenticate the user.
Updated · Editorial approach and simulation limits
The Discover–Offer–Request–ACK exchange
A client that does not yet know a DHCP server can broadcast DHCPDISCOVER. A server may answer with DHCPOFFER, which proposes an address and configuration. The client then sends DHCPREQUEST to identify the offer it selected, and the server confirms the lease with DHCPACK. This familiar four-message sequence is often called DORA.
The messages include transaction and client identifiers so the exchange can be matched. The server identifier helps distinguish among offers. A DHCPNAK can indicate that the requested configuration is not valid for the client’s current network; it is not the same as a silent timeout.
Lease options configure more than an IP address
A DHCP response can provide a subnet mask, default router, DNS resolver addresses, lease duration and other options. These values describe configuration supplied by the server. They do not prove that the router is reachable, that a DNS answer is correct, or that the client can access the public Internet.
DHCP uses UDP and can be relayed when the client and server are on different IP subnets. A relay agent forwards the client’s request and identifies the originating network so a centralized server can choose the appropriate scope. A capture taken only at the client may not show the relay-to-server leg.
Renewal, address changes and captive portal discovery
A DHCP address is leased for a period rather than owned permanently. A client can renew the lease, rebind if its original server is unavailable, or obtain new configuration after moving networks. When troubleshooting, follow the lease state and transaction identifiers instead of treating every DHCP packet as a new login.
DHCP option 114 is used by RFC 8910 to advertise a Captive Portal API URI. That option helps a capable client discover portal status; it does not itself grant access or provide the user’s login page. Compare the address, DNS and portal options together when a device joins a restricted network.
Explore DHCP interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 2131: Dynamic Host Configuration Protocol. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all network protocols · Follow DHCP discovery into a captive portal