Technical guide
How DHCP Works
Learn the DHCP exchange, renewal and recovery steps that keep devices connected, then plan the public IPv4 capacity your customers need.
Plan your IPv4 expansionGet devices online without configuring every address
DHCP gives a device the address and network settings it needs when it joins a network. Your team manages the address pool centrally, while customers and colleagues connect without typing IP settings themselves.
The name means Dynamic Host Configuration Protocol. For IPv4, a server can supply an address, subnet mask, default gateway, DNS servers and a lease duration. A relay carries requests between a client subnet and a server elsewhere in your network.
How the four-message exchange works
A new DHCPv4 client typically uses the sequence known as DORA. Each step has a different job:
- Discover — DHCPDISCOVER. The device looks for a server, usually by broadcasting on its local network.
- Offer — DHCPOFFER. A server proposes an address and configuration.
- Request — DHCPREQUEST. The client requests the offer it selected, allowing other servers to identify its choice.
- Acknowledge — DHCPACK. The selected server confirms the lease and settings. The client checks the address before using it.
A returning client may request its previous address directly. Renewing an existing lease also follows a shorter exchange, so a full DORA cycle is not needed every time a connected device checks in.
Keep a working connection through renewal
A lease is a time-limited assignment, not a scheduled disconnection. Clients normally ask to extend it while it is still valid. A successful renewal lets the device keep working with the confirmed address.
If the original server does not respond, the client can try other servers during rebinding. If the lease actually expires without a renewal, it stops using that address and starts address acquisition again. See what happens when a DHCP lease expires for the recovery path.
Manage the pool around your customers
- Welcome new devices: monitor free addresses in each scope before busy periods.
- Reduce repeated setup: distribute consistent gateway and DNS settings from the server.
- Keep important devices findable: use reservations or carefully managed static addresses for equipment that needs a stable local address.
- Recover faster: retain lease records and correlate client identity, subnet and time with the reported connection problem.
DHCP reuses addresses after assignments end. The pool still needs enough capacity for simultaneous devices. Shortening a timer does not create extra public IPv4 addresses.
Dynamic, reserved or static?
| Method | Good fit | What your team manages |
|---|---|---|
| Dynamic DHCP | Client devices joining and leaving | A usable pool, lease duration and server reachability |
| DHCP reservation | A device that should receive a consistent address | The reservation and a working DHCP service |
| Static configuration | Infrastructure requiring an independently configured address | Correct host settings and exclusion from dynamic allocation |
A reservation still uses DHCP. It is not the same as entering a static address on the device, and it does not remove dependence on the DHCP service.
What changes with IPv6?
DHCPv6 is a separate protocol. An IPv6 network may use stateless address autoconfiguration, DHCPv6, or a combination for different settings. Router advertisements provide the information used for default-router discovery; do not assume the IPv4 DORA exchange applies unchanged.
Find the failed step before changing timers
If a device cannot obtain an address, check its link or Wi-Fi connection and VLAN first. Then inspect the matching DHCP scope, free-address count, relay path and server logs. For DHCPv4, check that the required UDP 67/68 traffic can reach the intended client, server and relay interfaces.
If an address is present but applications fail, check the supplied gateway and DNS settings as well. Record the current lease before forcing a release; releasing a working address can interrupt a remote session.
Protect the service that hands out settings
Use supported DHCP snooping and trusted-port settings to reduce rogue-server exposure. Pair address allocation with your network's authentication and access controls. A short lease is an address-management setting, not a way to revoke a compromised device's permission to connect.
For resilience, use the DHCP platform's supported redundancy design and verify lease-state coordination. Two uncoordinated servers using the same pool can create conflicts.
Give customer growth an address plan
DHCP handles local assignments. Public IPv4 supply is the capacity behind internet-facing customer services. Keep those decisions connected: forecast concurrent demand, plan your subnets, and secure the public addresses needed for the next launch.
LARUS brings Unlimited IPv4 and first-party Continuity to that growth plan, keeping the address-supply conversation with the operator responsible for it. Your team can focus on customer services while planning capacity beyond today's pool.
Questions operators ask
Will DHCP always give a device a different address?
No. A client can renew or receive its previous address. A reservation provides a managed way to request a consistent assignment.
Can one device have more than one DHCP address?
Yes. A device with multiple interfaces or network connections can have separate assignments. Think in terms of clients and interfaces rather than one address per physical device.
Does DHCP eliminate every address conflict?
It helps coordinate allocation. Conflicting static settings, overlapping pools or inconsistent server state can still cause duplicate use.
Protocol references: DHCPv4 (RFC 2131) and DHCPv6 (RFC 9915). Default-router discovery is described in RFC 4861.
Room for your next launch
Give your next customers room to grow.
Build with Unlimited IPv4 and LARUS Continuity. Plan the public address capacity for your next service, location or customer launch with LARUS directly.