DHCP (Dynamic Host Configuration Protocol) automates the process of assigning IP addresses and network configuration to devices on a network. Without DHCP, every device would need to be manually configured with an IP address, subnet mask, default gateway, and DNS servers — a tedious and error-prone process, especially in networks with hundreds or thousands of devices. DHCP solves several problems: • Eliminates manual IP configuration for each device • Prevents IP address conflicts (two devices with the same IP) • Efficiently manages limited IP address pools • Automatically provides all necessary network parameters • Allows devices to move between networks seamlessly Almost every network uses DHCP. When you connect your phone to Wi-Fi, plug in an Ethernet cable at the office, or connect to a hotel network, DHCP is working behind the scenes to give your device the network configuration it needs to communicate. DHCP operates on a client-server model. The DHCP server maintains a pool of available IP addresses and configuration parameters. DHCP clients (your devices) request configuration when they connect to the network.

DHCP uses a four-step process known as DORA (Discover, Offer, Request, Acknowledge) to assign IP addresses: Step 1 — DHCP Discover: When a device connects to a network without an IP address, it broadcasts a DHCP Discover message to the entire local network (destination: 255.255.255.255, source: 0.0.0.0). This is a broadcast because the client does not yet know the DHCP server's address. The message essentially says: "Is there a DHCP server on this network? I need an IP address." Step 2 — DHCP Offer: Any DHCP server on the network that receives the Discover message responds with a DHCP Offer. This offer includes an available IP address, subnet mask, default gateway, DNS servers, and a lease duration. If multiple DHCP servers exist, the client may receive multiple offers. Step 3 — DHCP Request: The client selects one offer (typically the first one received) and broadcasts a DHCP Request message. This broadcast serves two purposes: it tells the chosen server "I accept your offer" and tells any other servers "I am declining your offers." The request includes the server identifier of the chosen server. Step 4 — DHCP Acknowledge: The chosen DHCP server sends a DHCP Acknowledge (ACK) message confirming the assignment. At this point, the client configures its network interface with the provided parameters and can begin communicating on the network. This entire process typically completes in less than one second. If the server cannot fulfill the request (for example, if the offered address was taken by another device in the meantime), it sends a DHCP NAK (negative acknowledgment), and the client must restart the DORA process.

DHCP does not permanently assign IP addresses — it leases them for a specific duration. This lease mechanism ensures that addresses are returned to the pool when devices leave the network. Lease Duration: • Typical home network: 24 hours • Enterprise wired network: 8 hours to 7 days • Enterprise wireless network: 4-8 hours • Guest network: 1-4 hours • DHCP lease time is configurable by the administrator Lease Renewal Process: At 50% of the lease duration (T1 timer), the client attempts to renew its lease by sending a DHCP Request directly to the server that issued the lease. If successful, the lease timer resets. At 87.5% of the lease duration (T2 timer), if the original server has not responded, the client broadcasts a renewal request to any DHCP server on the network. If the lease expires without renewal, the client must release the IP address and restart the DORA process. During this brief period, the device loses network connectivity. Best practices for lease duration: • Shorter leases (1-4 hours): Guest networks, public Wi-Fi, environments with many transient devices • Medium leases (8-24 hours): Standard office environments • Longer leases (3-7 days): Stable environments with few device changes • Very long leases: Not recommended — they can exhaust the address pool if devices leave without releasing their lease

DHCP administrators use scopes and reservations to manage address assignment: DHCP Scope: A scope defines the range of IP addresses that a DHCP server can assign on a particular subnet. For example: • Subnet: 192.168.1.0/24 • Scope range: 192.168.1.100 to 192.168.1.200 (101 addresses available) • Excluded addresses: 192.168.1.1-99 (reserved for static assignments like servers, printers, routers) A scope also includes the configuration options provided to clients: • Default gateway (Option 3) • DNS servers (Option 6) • Domain name (Option 15) • NTP servers (Option 42) • TFTP server for PXE boot (Option 66) DHCP Reservations: A reservation assigns a specific IP address to a specific device based on its MAC address. The device still uses DHCP (DORA process), but always receives the same IP address. This is useful for: • Printers (users bookmark the printer's IP-based management page) • Network-attached storage (NAS) devices • IP cameras • Servers that need consistent addresses but you want centralized management Reservations provide the consistency of static addressing with the centralized management benefits of DHCP. If a device is replaced, you only need to update the MAC address in the reservation rather than reconfiguring the new device.

DHCP issues are among the most common network problems IT professionals encounter: Device gets 169.254.x.x address (APIPA): • Cause: The device could not reach a DHCP server • Check: Is the DHCP server running? Is there network connectivity between client and server? • Check: Has the DHCP scope run out of available addresses? • Check: Is there a DHCP relay agent configured if the server is on a different subnet? • Fix: Verify server status, check scope availability, verify network path IP Address Conflicts: • Cause: Two devices have the same IP address • Common scenario: A device with a static IP that falls within the DHCP scope range • Prevention: Exclude statically-assigned addresses from the DHCP scope • Fix: Release and renew the conflicting DHCP client, or change the static assignment Rogue DHCP Server: • Cause: An unauthorized DHCP server on the network (often a user's personal router plugged in incorrectly) • Symptoms: Devices receive wrong IP addresses, gateways, or DNS servers • Detection: Check the DHCP server address in ipconfig /all — if it is not your authorized server, you have a rogue • Prevention: Enable DHCP snooping on managed switches to block unauthorized DHCP servers • Fix: Locate and disconnect the rogue device Scope Exhaustion: • Cause: More devices requesting addresses than the scope has available • Symptoms: New devices cannot connect, existing devices work fine • Check: Review DHCP server statistics for available addresses • Fix: Expand the scope range, reduce lease times, or remove stale leases DHCP Relay Issues: • Cause: DHCP broadcasts do not cross router boundaries without a relay agent • Symptoms: Devices on remote subnets cannot get DHCP addresses • Fix: Configure ip helper-address on the router interface pointing to the DHCP server