DHCP
Also known as: Dynamic Host Configuration Protocol
DHCP, the Dynamic Host Configuration Protocol, is the system that automatically gives devices an IP address and other network settings, such as the router's address and DNS servers, when they join a network.
Without it, you'd need to type these settings into every phone and laptop by hand. While DHCP is invisible when it works, a DHCP problem is a classic reason a device says it's connected to Wi-Fi but has no internet.
DHCP, explained at three levels
At home
DHCP works like the front desk of a hotel. When you arrive, the clerk assigns you a room number, tells you where breakfast is served, and says when checkout is. When your phone joins a network, it asks the DHCP server, usually your router, for the same kind of information: an address to use, the way out to the internet, and how long it can keep that address.
At work
DHCP, the Dynamic Host Configuration Protocol, is a service that automatically gives every device on a network its IP address, default gateway, and DNS servers. Without it, IT staff would configure each laptop, phone, and printer by hand, and mistakes would cause address conflicts. Businesses depend on it because if the DHCP service fails, new devices cannot get online at all.
At home
DHCP is a four-step conversation often remembered as DORA. Your phone broadcasts a Discover message asking for any DHCP server. The router replies with an Offer of a free address. The phone sends a Request to accept it, and the router confirms with an Acknowledgement. The address is a lease, often for a day, and the phone renews it about halfway through. If no server answers, the device gives itself a 169.254 address, which only works locally.
At work
A DHCP server manages scopes, which are pools of addresses for each subnet, along with lease times and options such as default gateway, DNS servers, and domain name. Reservations tie a fixed address to a device's MAC address, giving printers and cameras predictable addresses while keeping management central. Because DHCP requests are broadcasts that stay within one VLAN, routers use a DHCP relay, also called an IP helper, to forward them to a central server such as Windows Server.
At home
DHCP trusts whoever answers first. Your device broadcasts a request and accepts the first offer it hears, with no proof the server is legitimate. That makes it easy for a misconfigured second router, or an attacker, to hand out wrong settings, such as a fake DNS server that redirects you. Lease timing also explains odd glitches when devices hold stale addresses after a change. While DHCP is wonderfully simple, in my view that simplicity is also its weakness.
At work
DHCP's main risks are rogue servers, pool exhaustion, and single points of failure. Switches counter rogue servers with DHCP snooping, which trusts replies only from designated ports and builds a binding table used by dynamic ARP inspection. Guest networks with long leases run out of addresses, so lease times should match visit length. Windows Server DHCP failover or paired ISC Kea servers provide redundancy. On IPv6, DHCPv6 works alongside router advertisements, which need their own protection, called RA Guard.
Real-world examples
At home
Sophie's new smart TV said it was connected to Wi-Fi but had no internet. Restarting the router let DHCP assign a fresh address, and it started working.
At work
Carlos manages IT at a Calgary school. He shortened DHCP lease times on the guest network so addresses freed up quickly when visitors left after events.
How it compares
| feature | DHCP | Static IP address |
|---|---|---|
| Setup | Automatic | Typed in manually |
| Address can change | Yes, unless reserved | No |
| Best for | Phones, laptops, guests | Servers, some network gear |
| Error risk | Low | Typos and conflicts |
DHCP is automatic and flexible. Static addresses are fixed and manual.
For analysts
I'd use DHCP reservations instead of manual static addresses for printers and key devices. They stay predictable while still being centrally managed.
History & origin
Before automatic configuration, network administrators assigned addresses manually. The Bootstrap Protocol (BOOTP), published in 1985, let diskless computers get addresses at startup. DHCP extended BOOTP and was published by the IETF in 1993, with the main version, RFC 2131, edited by Ralph Droms of Bucknell University in 1997. It became built into routers, servers, and operating systems, and a version for IPv6, DHCPv6, followed in 2003. In my view, DHCP is one of those quiet protocols that made networking accessible to everyone.