On this page & study actions
Assessed progress
Sign in and complete the verified MCQs to track mastery.
Unit 6: Application Layer2 min read
The Dynamic Host Configuration Protocol (DHCP) is an application-layer service designed to automate the assignment of network configurations to hosts on a TCP/IP network. By dynamically allocating logical identities, DHCP eliminates the administrative overhead and errors associated with manual host configuration.
Every host participating in a classless inter-domain routing (CIDR) environment requires a specific set of parameters to communicate beyond its immediate physical layer link. Without these parameters, transport protocols (TCP/UDP) and routing layers (IP) cannot bind sockets or route payloads.
To establish connectivity, a device requires four critical pieces of network configuration:
Historically, the Bootstrap Protocol (BOOTP) (RFC 951) was used to deliver these configuration sets. However, BOOTP possessed significant structural limitations:
+-------------------------------------------------------------+
| BOOTP (Static Mapping) |
| [MAC Address: 00:1A:2B...] <======> [Static IP: 192.168.1.5] |
| - No temporal leasing |
| - High administrative overhead for dynamic devices |
+-------------------------------------------------------------+
||
\/
+-------------------------------------------------------------+
| DHCP (Dynamic & Static Mapping) |
| - Temporal lease pools |
| - State machine tracking client lifecycles |
| - Dynamic integration with DNS systems |
+-------------------------------------------------------------+While BOOTP relied on rigid, static tables mapping a client's Media Access Control (MAC) address to a pre-allocated IP address, DHCP introduces temporal allocation. It permits the reuse of address spaces via dynamic leases, preventing address exhaustion in dense or transient client environments (such as corporate wireless networks).
DHCP operates within the client-server paradigm and is encapsulated within the User Datagram Protocol (UDP) transport layer.
Unlike standard application-layer protocols where both client and server negotiate over a single port, DHCP enforces a strict asymmetric port design:
6768+-----------------------+ +-----------------------+
| DHCP Client | | DHCP Server |
| (Source Port: 68) | -----------------> | (Destination Port:67)|
| | <----------------- | |
| (Dest Port: 68) | | (Source Port: 67) |
+-----------------------+ +-----------------------+To understand why this separation exists, consider the nature of a host initial boot sequence:
255.255.255.255.67, any broadcast query from a client would trigger the network stacks of all other servers on the subnet. This would create unnecessary application processing cycles.68, the host operating system instantly filters and identifies incoming configuration offers without routing them through standard server listeners.If the DHCP client and server reside within the same physical broadcast domain (local network), the transaction is direct. However, enterprise networks are typically divided into multiple subnets separated by physical routers. Since standard routers drop broadcast packets (destination 255.255.255.255), DHCP broadcasts cannot naturally cross subnets.
To resolve this limitation without deploying a dedicated DHCP server on every subnet, network administrators deploy a DHCP Relay Agent (often referred to as an IP Helper). The relay agent is a lightweight process running on the local router interface.
[ DHCP Client ]
|
| 1. Broadcast (Src: 0.0.0.0, Dst: 255.255.255.255)
v
+------------------+
| DHCP Relay Agent | (Router Interface)
+------------------+
|
| 2. Unicast Conversion (Src: 192.168.1.1, Dst: 10.0.0.5)
| Modifies 'giaddr' to 192.168.1.1
v
[ Router / WAN ]
|
v
+------------------+
| DHCP Server | (Host IP: 10.0.0.5)
+------------------+The process operates as follows:
DHCPDISCOVER packet on port 67 within its local subnet.192.168.1.1) into the Gateway IP Address (giaddr) field of the DHCP packet header.10.0.0.5) across the routed network.giaddr field. It uses this field to determine which subnet pool to select an address from.giaddr. The Relay Agent then extracts the payload and broadcasts it back onto the client's local network on port 68.DHCP uses a fixed-length header structure followed by a variable-length options field. This design ensures backward compatibility with BOOTP while supporting extensibility.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| op (1) | htype (1) | hlen (1) | hops (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| xid (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| secs (2) | flags (2) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ciaddr (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| yiaddr (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| siaddr (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| giaddr (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| chaddr (16) |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sname (64) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| file (128) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| options (var) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+The key fields within this header include:
1 for boot request (client to server), 2 for boot reply (server to client).BOUND or RENEWING states if it already has a valid IP address.DHCP Option fields utilize a Tag-Length-Value (TLV) format:
+--------------+--------------+-----------------------+
| Tag (1 Byte)|Length (1 Byte| Value (n Bytes) |
+--------------+--------------+-----------------------+To designate the message type, Option 53 is appended to the packet. The value byte of Option 53 dictates the phase of the transaction:
1: DHCPDISCOVER (Client broadcast to locate servers)2: DHCPOFFER (Server response offering parameters)3: DHCPREQUEST (Client request to lease offered parameters)4: DHCPDECLINE (Client notification that an IP is already in use)5: DHCPACK (Server acknowledgment validating the lease)6: DHCPNAK (Server negative acknowledgment denying the lease)7: DHCPRELEASE (Client notification relinquishing an IP address)Other essential options include Option 1 (Subnet Mask), Option 3 (Router List), and Option 6 (Domain Name Server List).
DHCP supports two primary address allocation paradigms:
chaddr (MAC) to a specific IP address. The server reserves this address exclusively for that device.Client (0.0.0.0) Server (192.168.1.254)
| |
| ---------- 1. DHCPDISCOVER (Broadcast) -----------> |
| |
| <--------- 2. DHCPOFFER (Unicast/Broadcast) ------- | [Offers yiaddr]
| |
| ---------- 3. DHCPREQUEST (Broadcast) ------------> | [Confirms lease]
| |
| <--------- 4. DHCPACK (Unicast/Broadcast) --------- | [Locks lease]
| |DHCPDISCOVER packet searching for active DHCP servers.DHCPOFFER containing the proposed yiaddr and lease parameters.DHCPREQUEST to accept the selected offer. Broadcasting this step informs all other offering servers that their proposals were declined, allowing them to release their reserved IPs back into their pools.DHCPACK to finalize the lease.The lifetime of a leased IP is governed by a state machine tracking three key timers:
+-------------+
| INIT | <------------------------------------+
+-------------+ |
| |
Send | DHCPDISCOVER |
v |
+-------------+ |
| SELECTING | |
+-------------+ |
| |
Receive | DHCPOFFER, |
Send | DHCPREQUEST |
v |
+-------------+ |
| REQUESTING | |
+-------------+ |
| |
Receive | DHCPACK | Lease Expired
v | (T3 Exceeded)
+-------------+ |
+-------> | BOUND | |
| +-------------+ |
| | |
| | T1 Expired (Send Unicast DHCPREQUEST) |
| v |
| +-------------+ |
| | RENEWING | -------------------------------------+
DHCPDISCOVER and enters the SELECTING state.DHCPOFFER replies. Once it selects an offer, it sends a DHCPREQUEST and transitions to the REQUESTING state.DHCPACK. When received, the client configures its network interface, initializes its and timers, and enters the state.In early network architectures, DNS record mapping was entirely static. This model breaks down when DHCP dynamically changes host IP addresses, as names in the DNS zone files would point to stale, incorrect IPs.
The Dynamic Domain Name System (DDNS) protocol resolves this issue by integrating DHCP with primary DNS servers:
[ Client Device ] --(1) DHCPREQUEST--> [ DHCP Server ]
|
Allocates IP: 192.168.1.50
|
v
(2) Sends DDNS Update
|
v
+------------------+
| Primary DNS Server|
| (Updates Zone) |
+------------------+workstation-01) within the DHCP client options payload.To ground these conceptual mechanisms, here is a practical configuration example from a Cisco IOS environment. This illustrates the creation of an address pool, static bindings, and exclusion zones.
! 1. Exclude high-value static infrastructure IPs from the dynamic pool
ip dhcp excluded-address 192.168.1.1 192.168.1.20
ip dhcp excluded-address 192.168.1.250 192.168.1.254
! 2. Define the main dynamic lease pool
ip dhcp pool CORPORATE_LAN
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 8.8.8.8 8.8.4.4
domain-name kophub.internal
lease 1 12 0 ! Lease duration set to 1 day, 12 hours, 0 minutes
! 3. Configure a static reservation mapping for a network printer
ip dhcp pool PRINTER_RESERVATION
host 192.168.1.15 255.255.255.0
client-identifier 0100.1a2b.3c4d.5e ! 01 prefix followed by the printer's MAC addressThis configuration establishes:
.1 to .20 and .250 to .254 ranges, preserving them for routers, gateways, and switches.192.168.1.0/24 subnet and configures client devices with their default gateway, DNS servers, and a custom lease duration of 36 hours.00:1A:2B:3C:4D:5E always receives the IP address 192.168.1.15.67 for servers and port 68 for clients to prevent packet loops and simplify client-side filtering.The four critical pieces of network configurations (IP address, subnet mask, default router, and domain name server) required for a host to operate on a modern TCP/IP network.
The utilization of two distinct UDP ports (port 67 for the server and port 68 for the client) to prevent network-wide loopbacks and unnecessary processing overhead.
Intermediate helper agents that forward client DHCP broadcast messages across physical router boundaries to a remote server using unicast routing.
The state machine mechanics governing how a client requests, binds, renews (at T1 = 0.5L), and rebinds (at T2 = 0.875L) its temporal IP configuration.
The collaborative mechanism where a DHCP server dynamically registers a newly allocated IP and host name with a primary DNS server to maintain up-to-date mappings.
Test your understanding with 5 questions
Which of the following represents the complete set of parameters a host must normally obtain during configuration to communicate seamlessly with local and remote networks?
Why does the DHCP protocol use two distinct UDP port numbers (67 for the server and 68 for the client) instead of a single well-known port?
A DHCP client has successfully leased an IP address for a duration of L = 24 hours. At what time offset will the client transition to the RENEWING state and attempt to contact the leasing server?
What parameter must a DHCP Relay Agent populate in the client’s original DHCPDISCOVER broadcast frame before forwarding it to a remote DHCP server?
What occurs if a DHCP client's renewal timer T1 expires, and it receives no response from its original DHCP server by the time the rebinding timer T2 (87.5% of lease time) is reached?
8: DHCPINFORM (Client request for local parameters without acquiring an IP)RENEWING state. It sends a unicast DHCPREQUEST directly to the original leasing server.
DHCPACK, the client resets its timers and returns to the BOUND state.REBINDING state. It broadcasts a DHCPREQUEST to any available DHCP server.
DHCPACK, the client configures the new parameters and returns to the BOUND state.INIT state to request a new assignment.INIT6 Modules
6 Modules