DHCP (Dynamic Host Configuration Protocol) is a network management protocol used on IP networks to automatically assign IP addresses and other configuration parameters to devices, allowing them to join and communicate on a network without manual setup.
DHCP
DHCP (Dynamic Host Configuration Protocol), standardized in RFC 2131, is the protocol that lets a device join an IP network without anyone configuring it by hand. When a client connects, it broadcasts a request and a DHCP server leases it an IP address along with the supporting settings — subnet mask, default gateway, and DNS servers — it needs to communicate. It is one of the quiet foundations that makes plugging into a network “just work.”
- Automatic address assignment - Hands out IP addresses from a managed pool instead of static, manual configuration.
- Leases - Addresses are granted for a limited time and reclaimed, so scarce address space is reused efficiently.
- Configuration delivery - Distributes gateway, DNS, and other network parameters alongside the address.
- Client-server model - A DORA exchange (Discover, Offer, Request, Acknowledge) negotiates the lease between client and server.
DHCP rarely appears in an API contract itself, but it is infrastructure that API operations depend on. Every server, container host, and network device that fronts an API relies on DHCP or its static equivalent to be reachable, and DHCP data feeds the IP address management and network inventory systems that many infrastructure APIs expose. Understanding it matters when APIs govern or automate networks, where address allocation, DNS, and connectivity are the plumbing beneath the interface.
