DHCP – Dynamic Host Configuration Protocol Overview

1. What Is DHCP and Why Is It Used?

Dynamic Host Configuration Protocol (DHCP) is an application-layer protocol that automatically assigns IP addressing information to hosts on a network. Without DHCP, every device — every PC, phone, printer, and IoT sensor — would need its IP address, subnet mask, default gateway, and DNS server configured manually. On a network of even modest size, that becomes an enormous administrative burden.

DHCP operates on a client/server model. A DHCP server (a dedicated server, a router, or a Layer 3 switch) maintains a pool of available IP addresses and configuration parameters. A DHCP client (any host that needs network configuration) broadcasts a request and receives a lease automatically — typically in under a second.

Information DHCP Can Provide	DHCP Option Number	Notes
IP address	—	Assigned from the configured pool/scope
Subnet mask	Option 1	Defines the network boundary for the assigned IP
Default gateway	Option 3	The router address clients use to reach other networks
DNS server(s)	Option 6	Up to eight DNS server addresses can be provided
Domain name	Option 15	e.g., `company.local`
Lease time	Option 51	How long the client may keep the assigned IP address
TFTP server / boot file	Options 66 / 67	Used for PXE booting and IP phone firmware
NTP server	Option 42	Network Time Protocol server address — see NTP Configuration Lab

DHCP ports: DHCP uses UDP port 67 (server) and UDP port 68 (client). Because early DHCP messages are broadcasts (the client has no IP yet), DHCP cannot use TCP. See: Common Port Numbers

2. The DORA Process — How a Client Gets an IP Address

When a DHCP client needs an IP address it goes through a four-step exchange known as DORA: Discover → Offer → Request → Acknowledge. Each step is a distinct UDP message type. Understanding DORA — what each message does, who sends it, and what addressing it uses — is a core CCNA exam topic.

  DORA overview — new client joining the network:

  Client                                          DHCP Server
  ──────                                          ───────────
  "I need an IP address — is anyone there?"
  DHCPDISCOVER ──────────────────────────────────────────────►
  (broadcast: Src 0.0.0.0:68 → Dst 255.255.255.255:67)

                     "I have an address for you — here's an offer."
              ◄────────────────────────────────── DHCPOFFER
              (broadcast or unicast: offered IP, mask, gateway, DNS, lease)

  "I'll take that offer — formally requesting it."
  DHCPREQUEST ───────────────────────────────────────────────►
  (broadcast: Src 0.0.0.0:68 → Dst 255.255.255.255:67)
  (broadcast allows other DHCP servers to see the request
   and withdraw their offers)

                          "Confirmed — the address is yours."
              ◄────────────────────────────────── DHCPACK
              (confirms IP, mask, gateway, DNS, and lease duration)

  Client configures its interface with the leased parameters.
  IP address is now active.

Memory aid — DORA:
Discover — client broadcasts looking for a server
Offer — server proposes an IP address
Request — client formally asks for that specific offer
Ack — server confirms and delivers the lease

3. DORA — Each Message in Detail

Step 1 — DHCPDISCOVER

The client has no IP address yet, so it sends a broadcast to find any available DHCP server on the local segment. The source IP is 0.0.0.0 (the client has no address) and the destination is the limited broadcast 255.255.255.255.

  DHCPDISCOVER key fields:
  ┌────────────────────────────────────────────────────────────┐
  │ Source IP:       0.0.0.0                                   │
  │ Destination IP:  255.255.255.255 (limited broadcast)       │
  │ Source Port:     UDP 68  (DHCP client)                     │
  │ Destination Port:UDP 67  (DHCP server)                     │
  │ Client MAC:      AA:BB:CC:DD:EE:FF  (identifies the client)│
  │ Message type:    DHCPDISCOVER (Option 53 = 1)              │
  └────────────────────────────────────────────────────────────┘
  Sent as: Layer 2 broadcast (FF:FF:FF:FF:FF:FF)

Step 2 — DHCPOFFER

The DHCP server responds with an offer containing a proposed IP address, subnet mask, default gateway, DNS server, and lease duration. If the client does not yet have an IP, the offer may be sent as a broadcast or unicast depending on the broadcast flag in the Discover message.

  DHCPOFFER key fields:
  ┌────────────────────────────────────────────────────────────┐
  │ Source IP:       192.168.1.1   (DHCP server)               │
  │ Destination IP:  255.255.255.255 (or unicast to client MAC)│
  │ Offered IP:      192.168.1.100                             │
  │ Subnet mask:     255.255.255.0                             │
  │ Default gateway: 192.168.1.1                               │
  │ DNS server:      8.8.8.8                                   │
  │ Lease time:      86400 seconds (24 hours)                  │
  │ Message type:    DHCPOFFER (Option 53 = 2)                 │
  └────────────────────────────────────────────────────────────┘
  The server marks 192.168.1.100 as "tentatively reserved."

Step 3 — DHCPREQUEST

The client sends a broadcast to formally request the offered address and to inform all other DHCP servers on the segment that it is accepting a specific offer. This broadcast allows any DHCP servers that sent competing offers to release their tentatively reserved addresses back to their pools.

  DHCPREQUEST key fields:
  ┌────────────────────────────────────────────────────────────┐
  │ Source IP:       0.0.0.0  (still no confirmed IP yet)      │
  │ Destination IP:  255.255.255.255 (broadcast)               │
  │ Requested IP:    192.168.1.100  (Option 50)                │
  │ Server ID:       192.168.1.1    (Option 54 — chosen server)│
  │ Message type:    DHCPREQUEST (Option 53 = 3)               │
  └────────────────────────────────────────────────────────────┘
  Broadcast ensures all competing servers see the selection.

Step 4 — DHCPACK

The chosen DHCP server sends a final acknowledgement that confirms the IP address lease and delivers all configuration parameters. The client applies the settings to its network interface and is ready to communicate.

  DHCPACK key fields:
  ┌────────────────────────────────────────────────────────────┐
  │ Source IP:       192.168.1.1   (DHCP server)               │
  │ Destination IP:  255.255.255.255 (or unicast)              │
  │ Leased IP:       192.168.1.100                             │
  │ Subnet mask:     255.255.255.0                             │
  │ Default gateway: 192.168.1.1                               │
  │ DNS server:      8.8.8.8                                   │
  │ Lease time:      86400 seconds                             │
  │ Message type:    DHCPACK (Option 53 = 5)                   │
  └────────────────────────────────────────────────────────────┘
  Client configures interface → ready to communicate.

DHCPNAK (Negative Acknowledgement): If the server cannot honour the request — for example, if the requested IP is no longer available or the client has moved to a different subnet — it sends a DHCPNAK instead of a DHCPACK. The client must restart the DORA process from the beginning upon receiving a NAK.

Message	Sent By	Type	Source IP	Destination IP	Purpose
DHCPDISCOVER	Client	Broadcast	0.0.0.0	255.255.255.255	Find available DHCP servers
DHCPOFFER	Server	Broadcast / Unicast	Server IP	255.255.255.255	Propose an IP address and parameters
DHCPREQUEST	Client	Broadcast	0.0.0.0	255.255.255.255	Formally request the offered IP; inform other servers
DHCPACK	Server	Broadcast / Unicast	Server IP	255.255.255.255	Confirm lease; deliver all IP configuration
DHCPNAK	Server	Broadcast	Server IP	255.255.255.255	Reject request; client must restart DORA
DHCPRELEASE	Client	Unicast	Client IP	Server IP	Client voluntarily returns its leased IP
DHCPINFORM	Client	Unicast	Client IP	Server IP	Client already has IP; requests only other config options

See full detail: How DHCP Works – Full Guide

4. DHCP Lease Time

The lease time defines how long a client is permitted to use an assigned IP address before it must renew the lease with the DHCP server. Lease management is critical — if a lease expires and is not renewed, the client loses its IP configuration and must restart DORA.

Lease Renewal Timeline

  Lease lifecycle (example: 24-hour / 86400-second lease):

  T=0          T=50% (12h)      T=87.5% (21h)    T=100% (24h)
  │            │                │                 │
  ├────────────┼────────────────┼─────────────────┤
  │            │                │                 │
  Lease        T1: Renewal      T2: Rebinding     Lease
  Granted      (unicast to      (broadcast to     Expires
               original server) any DHCP server)  (client loses IP)

  T1 (50% of lease) — DHCPREQUEST sent directly (unicast) to the
  original DHCP server asking to renew. If the server responds with
  DHCPACK, the lease is extended from the current time.

  T2 (87.5% of lease) — If T1 renewal failed, client broadcasts a
  DHCPREQUEST to ANY DHCP server on the segment (rebinding). The
  client is still using the old IP and hoping any server will renew it.

  T=100% — If neither T1 nor T2 renewal succeeded, the lease expires.
  The client MUST stop using the IP address immediately and restart the
  full DORA process from DHCPDISCOVER.

Lease Duration	Typical Use Case	Considerations
Short (1–4 hours)	Guest Wi-Fi, hotspots, high-turnover environments	Addresses return to pool quickly; higher DHCP traffic due to frequent renewals
Medium (8–24 hours)	Corporate office workstations	Common default; balances address reuse with renewal overhead
Long (3–8 days)	Servers, printers, fixed infrastructure	Reduces renewal traffic; devices keep address across reboots
Infinite	Static-like assignments for specific hosts via DHCP	Address is never returned to pool; effectively a dynamic static assignment

CCNA exam tip: Know the two renewal timers — T1 at 50% (unicast renewal to original server) and T2 at 87.5% (broadcast rebinding to any server). At 100% the lease expires and the client must restart DORA completely.

5. DHCP Scope, Pool, and Exclusions

A DHCP scope (or pool in Cisco IOS terminology) defines the range of IP addresses and configuration options that a DHCP server will assign to clients on a given subnet. Configuring the scope correctly is the foundation of any DHCP deployment. A solid understanding of subnetting is essential for calculating correct pool ranges and exclusions.

Key Scope Components

Component	Description	Example
Network / Range	The subnet from which addresses are assigned	`192.168.1.0 /24`
Excluded addresses	Addresses within the scope that the DHCP server will NOT assign — reserved for routers, switches, servers, and printers with static IPs	`192.168.1.1 – 192.168.1.20`
Default gateway	Pushed to clients as Option 3	`192.168.1.1`
DNS server	Pushed to clients as Option 6	`8.8.8.8`
Lease time	How long clients may keep the assigned address	1 day (86400 seconds)
Domain name	Pushed to clients as Option 15	`company.local`

DHCP Exclusions — Why They Matter

Without exclusions, the DHCP server might assign an address already statically configured on a router, switch SVI, server, or printer — causing an IP address conflict. Exclusions must be configured before the pool so the server never hands out those addresses.

  Best practice address planning for 192.168.1.0/24:

  192.168.1.0         — Network address (unusable)
  192.168.1.1         — Default gateway (router) — EXCLUDE
  192.168.1.2         — Layer 3 switch SVI       — EXCLUDE
  192.168.1.3–10      — Reserved for servers      — EXCLUDE
  192.168.1.11–20     — Reserved for printers     — EXCLUDE
  ─────────────────────────────────────────────────────────
  192.168.1.21–254    — DHCP pool (234 available addresses)
  192.168.1.255       — Broadcast (unusable)

Cisco IOS DHCP Server Configuration

  ! Step 1 — Exclude addresses BEFORE defining the pool:
  Router(config)# ip dhcp excluded-address 192.168.1.1 192.168.1.20

  ! Step 2 — Create and name the DHCP pool:
  Router(config)# ip dhcp pool LAN_POOL

  ! Step 3 — Define the network (scope):
  Router(dhcp-config)# network 192.168.1.0 255.255.255.0

  ! Step 4 — Set the default gateway (Option 3):
  Router(dhcp-config)# default-router 192.168.1.1

  ! Step 5 — Set the DNS server (Option 6):
  Router(dhcp-config)# dns-server 8.8.8.8 8.8.4.4

  ! Step 6 — Set the domain name (Option 15):
  Router(dhcp-config)# domain-name company.local

  ! Step 7 — Set the lease time (days hours minutes):
  Router(dhcp-config)# lease 1 0 0

  ! Verify DHCP pool and bindings:
  Router# show ip dhcp pool
  Router# show ip dhcp binding
  Router# show ip dhcp conflict
  Router# show ip dhcp statistics

Critical order: Always configure ip dhcp excluded-address statements before creating the pool. If the router boots and the pool is active before exclusions are applied, it may hand out addresses that conflict with statically-configured devices.

See full detail: DHCP Configuration Guide | DHCP Server Configuration Lab

6. DHCP Address Bindings and Conflicts

A DHCP binding is the record of a leased IP address and the client that holds it, identified by the client's MAC address. The DHCP server stores all active bindings in memory and uses them to avoid assigning the same address twice.

  Router# show ip dhcp binding

  IP address       Client-ID / Hardware address   Lease expiration        Type
  192.168.1.21     0100.1122.3344.55              Mar 18 2026 09:00 AM    Automatic
  192.168.1.22     0100.aabb.ccdd.ee              Mar 18 2026 10:30 AM    Automatic
  192.168.1.23     0100.dead.beef.01              Infinite                Manual

DHCP Conflicts

A DHCP conflict occurs when the DHCP server tries to assign an address that is already in use on the network. Cisco IOS uses ping (before offering) and gratuitous ARP (by the client after receiving the offer) to detect conflicts. If a conflict is found, the address is removed from the pool and logged.

  ! View addresses that were detected as conflicted and removed from the pool:
  Router# show ip dhcp conflict

  IP address        Detection method   Detection time
  192.168.1.25      Ping               Mar 17 2026 08:14 AM

  ! Clear a specific conflict so the address can be used again:
  Router# clear ip dhcp conflict 192.168.1.25

  ! Clear all conflicts:
  Router# clear ip dhcp conflict *

7. DHCP Relay Agent — ip helper-address

DHCP relies on broadcasts for the Discover and Request messages. Broadcasts do not cross router boundaries — they are confined to the local subnet. This creates a problem: if the DHCP server is on a different subnet (or a centralised server farm), clients on remote subnets cannot reach it via broadcast.

The solution is a DHCP Relay Agent. The relay agent is configured on the router interface that faces the client subnet. It intercepts the DHCP broadcast from the client and forwards it as a unicast packet directly to the DHCP server's IP address. The server receives the forwarded request, allocates an address from the appropriate scope, and sends the reply back through the relay agent to the client.

DHCP Relay — How It Works

  Topology: DHCP server is centrally located; clients are on remote subnets.

  [Client 192.168.10.x]       [Router]            [DHCP Server 10.0.0.2]
  Subnet: 192.168.10.0/24     Gi0/0: 192.168.10.1  Subnet: 10.0.0.0/24
                              Gi0/1: 10.0.0.1

  Step 1: Client broadcasts DHCPDISCOVER
          Src: 0.0.0.0   Dst: 255.255.255.255
          → Received by Router Gi0/0 (ip helper-address configured)

  Step 2: Router (relay agent) converts broadcast to unicast:
          Src: 192.168.10.1 (router's inside interface)
          Dst: 10.0.0.2     (DHCP server unicast)
          → Also inserts the client's subnet info (giaddr field = 192.168.10.1)

  Step 3: DHCP server sees giaddr = 192.168.10.1
          → Allocates from the 192.168.10.0/24 scope (not its own subnet)
          → Sends DHCPOFFER back to relay agent (unicast to 192.168.10.1)

  Step 4: Relay agent forwards DHCPOFFER to client (broadcast on Gi0/0)

  Step 5: Same relay process for DHCPREQUEST and DHCPACK
          → Client receives full IP configuration

Configuring ip helper-address

  ! Configure ip helper-address on the router interface facing the clients:
  Router(config)# interface GigabitEthernet0/0
  Router(config-if)# ip address 192.168.10.1 255.255.255.0
  Router(config-if)# ip helper-address 10.0.0.2

  ! If clients are on multiple VLANs (SVIs on a Layer 3 switch):
  ! See: Inter-VLAN Routing (Layer 3 Switch)
  Switch(config)# interface vlan 10
  Switch(config-if)# ip address 192.168.10.1 255.255.255.0
  Switch(config-if)# ip helper-address 10.0.0.2

  Switch(config)# interface vlan 20
  Switch(config-if)# ip address 192.168.20.1 255.255.255.0
  Switch(config-if)# ip helper-address 10.0.0.2

  ! One ip helper-address per interface, pointing to the DHCP server.
  ! Multiple helper-addresses can be configured on one interface
  ! (forwards to multiple DHCP servers — useful for redundancy).

giaddr — Gateway IP Address field: The relay agent populates the giaddr field in the forwarded DHCP packet with its own interface IP address. The DHCP server uses giaddr to determine which scope to assign from — so it is critical that the DHCP server has a scope matching the giaddr subnet. If no matching scope exists, the server drops the request.

What ip helper-address Forwards

By default, ip helper-address forwards not just DHCP but also several other broadcast-based UDP services:

Service	UDP Port
DHCP / BOOTP Server	67
DHCP / BOOTP Client	68
TFTP	69
DNS	53 — see DNS Overview
NetBIOS Name Service	137
NetBIOS Datagram Service	138
TACACS	49
Time Protocol	37

See full detail: DHCP Relay Guide | DHCP Relay Agent Lab

8. DHCP Reservations — Binding a Specific IP to a MAC Address

A DHCP reservation (called a manual binding in Cisco IOS) ensures a specific host always receives the same IP address from DHCP, identified by its MAC address. This is useful for printers, servers, and IP phones that need a predictable address but whose configuration you still want managed centrally through DHCP.

  ! Create a manual DHCP binding for a specific host:

  Router(config)# ip dhcp pool PRINTER_01
  Router(dhcp-config)# host 192.168.1.50 255.255.255.0
  Router(dhcp-config)# hardware-address 00AA.BBCC.DD01
  Router(dhcp-config)# default-router 192.168.1.1
  Router(dhcp-config)# dns-server 8.8.8.8

  ! The host 00AA.BBCC.DD01 will always receive 192.168.1.50.
  ! Note: 192.168.1.50 should also be in the excluded range of the
  ! main pool to prevent it from being assigned to another host.

Reservation vs Static IP: A DHCP reservation gives a device the same IP every time via DHCP — the device's NIC is still set to "obtain IP automatically." A static IP is configured directly on the device's NIC. Reservations are easier to manage centrally; static IPs require touching each device individually. For IP phones, pair DHCP reservations with Voice VLAN and PortFast for fastest registration on power-up.

9. DHCP Snooping — Security Against Rogue DHCP Servers

DHCP Snooping is a Layer 2 security feature on Cisco switches that protects against rogue DHCP servers. Without it, any device connected to the network could run a DHCP server and respond to client Discover messages with malicious configuration — such as a fake default gateway (used in man-in-the-middle attacks).

DHCP Snooping divides switch ports into trusted and untrusted ports:

Port Type	DHCP Messages Allowed	Typical Assignment
Trusted	All DHCP messages (including DHCPOFFER, DHCPACK)	Uplinks to legitimate DHCP servers, router ports, trunk ports
Untrusted	Only client messages (DHCPDISCOVER, DHCPREQUEST). DHCPOFFER and DHCPACK are dropped — preventing rogue servers	All access ports connecting end-user devices

  ! Enable DHCP Snooping globally and per VLAN:
  ! See: VLANs Overview for VLAN concepts
  Switch(config)# ip dhcp snooping
  Switch(config)# ip dhcp snooping vlan 10

  ! Mark the uplink toward the legitimate DHCP server as trusted:
  Switch(config-if)# ip dhcp snooping trust

  ! Verify:
  Switch# show ip dhcp snooping
  Switch# show ip dhcp snooping binding

See full detail: DHCP Snooping Guide | DHCP Snooping & DAI Lab

10. DHCP Troubleshooting and Verification Commands

When clients fail to obtain IP addresses, a systematic approach to DHCP troubleshooting saves time. Start by confirming the client's perspective, then verify the server, then check relay if applicable.

Client-Side Verification

  Windows — check current IP configuration:
  C:\> ipconfig /all
  C:\> ipconfig /release        (release current DHCP lease)
  C:\> ipconfig /renew          (request a new lease — triggers DORA)

  Linux / macOS:
  $ ip address show             (or: ifconfig -a)
  $ sudo dhclient -r eth0       (release lease)
  $ sudo dhclient eth0          (request new lease)

Cisco Router / Switch Verification

  ! Show all active DHCP leases (bindings):
  Router# show ip dhcp binding

  ! Show DHCP pool configuration and utilisation:
  Router# show ip dhcp pool

  ! Show DHCP statistics (messages sent/received, conflicts):
  Router# show ip dhcp statistics

  ! Show addresses removed from pool due to conflicts:
  Router# show ip dhcp conflict

  ! Verify ip helper-address is configured correctly:
  Router# show ip interface GigabitEthernet0/0
  (look for "Helper address is 10.0.0.2")

  ! Real-time DHCP debug (use with care on busy networks):
  Router# debug ip dhcp server events
  Router# debug ip dhcp server packet
  Router# no debug all             (turn off all debugging)

Common DHCP Problems and Solutions

Symptom	Likely Cause	Fix
Client gets 169.254.x.x (APIPA)	No DHCP response received — server unreachable, pool exhausted, or relay misconfigured	Check pool availability, verify `ip helper-address`, check routing to server
IP address conflict	Statically-configured device uses an address in the DHCP pool	Add the conflicting address to `ip dhcp excluded-address`; run `clear ip dhcp conflict *`
Pool exhausted	All addresses in the scope are leased; new clients cannot get IPs	Shorten lease time, expand the pool, or add a second scope
Clients on remote subnet get no IP	Missing or incorrect `ip helper-address` on the inter-subnet router interface	Add `ip helper-address <server-IP>` to the correct interface; ensure DHCP server has a scope for the remote subnet
Rogue DHCP server handing out bad config	Unauthorised device running a DHCP server on the network	Enable DHCP Snooping on access switches; mark only legitimate server uplinks as trusted
Correct IP but no internet access	Wrong default gateway or DNS server pushed by DHCP	Verify `default-router` and `dns-server` in the pool configuration

Test Your Knowledge — DHCP Quiz

1. What does the acronym DORA stand for in the context of DHCP?

A. Distribute, Offer, Receive, Assign B. Discover, Order, Request, Acknowledge C. Discover, Offer, Request, Acknowledge D. Detect, Offer, Reserve, Activate

Correct answer is C. DORA describes the four-message exchange a DHCP client uses to obtain an IP address: the client sends a Discover broadcast, the server responds with an Offer, the client sends a Request to formally accept the offer, and the server confirms with an Acknowledge (ACK) containing the full IP configuration and lease duration.

2. Why does a DHCP client use 0.0.0.0 as the source IP address in the DHCPDISCOVER message?

A. The client has not yet been assigned an IP address, so it has no valid source address to use B. 0.0.0.0 is the DHCP server's reserved address C. It is a security feature to prevent the client's MAC from being tracked D. The client uses 0.0.0.0 to indicate it wants a specific IP address

Correct answer is A. At the time of the Discover, the client has not yet received an IP address from DHCP. Without a valid IP, it cannot place a real source address in the IP header. The address 0.0.0.0 is used as a placeholder meaning "this host, no address." The destination 255.255.255.255 ensures the broadcast reaches all devices on the local segment, including any DHCP servers.

3. Why is the DHCPREQUEST message sent as a broadcast even though the client already knows which server it wants to use?

A. The client does not know the DHCP server's IP address at this stage B. The client's IP stack does not support unicast until the ACK is received C. Broadcasts have higher priority than unicasts on the network D. The broadcast allows all other DHCP servers that sent competing offers to see that their offer was not accepted, so they can release their tentatively reserved addresses back to their pools

Correct answer is D. When multiple DHCP servers exist on a segment, all of them may respond to the Discover with an Offer, each tentatively reserving an address. The client accepts only one offer but must inform the others their offer was declined. By broadcasting the Request (which contains the chosen server's ID in Option 54), all DHCP servers can see the selection and release their tentative reservations.

4. A DHCP lease has a duration of 8 hours. At what point does the client first attempt to renew the lease, and how does it do so?

A. At 75% (6 hours) — by broadcasting a new DHCPDISCOVER B. At 50% (4 hours) — by sending a unicast DHCPREQUEST directly to the original DHCP server C. At 87.5% (7 hours) — by broadcasting a DHCPREQUEST to any available server D. At 100% (8 hours) — only when the lease fully expires

Correct answer is B. The first renewal attempt (T1) occurs at 50% of the lease time — at 4 hours for an 8-hour lease. The client sends a unicast DHCPREQUEST directly to the original DHCP server. If that fails, the second attempt (T2) occurs at 87.5% (7 hours) as a broadcast to any server. If both fail, at 100% the lease expires and the client must restart the full DORA process.

5. Why must `ip dhcp excluded-address` be configured before the DHCP pool on a Cisco router?

A. Cisco IOS will reject the pool configuration if exclusions are added afterward B. Exclusions can only be configured in global configuration mode, not inside the pool C. If the pool becomes active before exclusions are applied, the server may assign addresses already in use by static devices, causing IP conflicts D. Exclusions automatically delete existing bindings for those addresses when added

Correct answer is C. This is a best-practice requirement, not a technical IOS restriction. If a router boots and activates the pool before the exclusion statements are processed (due to configuration order), it could hand out an address like 192.168.1.1 (the router's own interface) or 192.168.1.5 (a server) — creating an IP conflict that disrupts connectivity. Always place exclusions first in the configuration. See: DHCP Configuration

6. What is the purpose of the `ip helper-address` command, and on which interface is it configured?

A. It configures the router as a DHCP relay agent, forwarding client DHCP broadcasts as unicast to the DHCP server. It is configured on the router interface facing the client subnet (not the server side) B. It enables the DHCP server function on the router and is configured globally C. It configures a static route to the DHCP server and is applied on the WAN interface D. It is configured on the DHCP server's interface to tell it which subnets to serve

Correct answer is A. ip helper-address is applied to the router interface on the client side of the network. When a DHCP broadcast arrives on that interface, the router intercepts it, adds the interface's IP address to the giaddr field (so the server knows which scope to use), and forwards the request as a unicast to the specified DHCP server address. See: DHCP Relay Guide

7. A client receives an IP address of 169.254.47.3 after booting. What does this indicate, and what should be checked first?

A. The client successfully obtained an address from a DHCP server on the 169.254.0.0 network B. The DHCP server assigned an APIPA address as a fallback because all normal pool addresses are excluded C. The client's NIC is statically configured with a 169.254.x.x address D. The client received no DHCP response and self-assigned an APIPA address (RFC 3927). Check that the DHCP server is reachable, the pool is not exhausted, and ip helper-address is configured if the server is on a different subnet

Correct answer is D. Addresses in the 169.254.0.0/16 range are APIPA (Automatic Private IP Addressing) addresses. A host assigns itself an APIPA address when it fails to receive a DHCP response after several attempts. It is never assigned by a DHCP server. Troubleshooting steps: confirm the DHCP server is running, the pool has available addresses, and (if on a different subnet) that ip helper-address is correctly configured. See: Troubleshooting DHCP Clients

8. What is the role of the `giaddr` field in a relayed DHCP packet, and why is it critical?

A. It carries the client's MAC address so the server can create a reservation B. It contains the relay agent's interface IP address, which the DHCP server uses to determine which scope to assign an address from. Without a matching scope for the giaddr subnet, the server drops the request C. It specifies the lease time the client is requesting D. It is the IP address the DHCP server will assign to the client

Correct answer is B. When a router relay agent forwards a DHCP Discover to the server, it fills the giaddr (Gateway IP Address) field with the IP address of its interface on the client-facing subnet. The DHCP server reads giaddr and selects the scope that matches that subnet. If no scope exists for that subnet, the server silently discards the request — a common misconfiguration problem. See: DHCP Relay Guide

9. What is the difference between a DHCP reservation (manual binding) and a statically configured IP address on a host?

A. There is no difference — both result in the same IP configuration B. A DHCP reservation requires the host to use a static IP; a manual binding does not C. A DHCP reservation is configured on the server, mapping a MAC address to a fixed IP; the host's NIC is still set to obtain an address automatically via DHCP. A static IP is configured directly on the host's NIC, with no DHCP involved D. A static IP is managed centrally on the DHCP server; a reservation is configured locally on the device

Correct answer is C. With a DHCP reservation, the server is configured with a MAC-to-IP mapping (using hardware-address and host commands in Cisco IOS). The client device itself is still set to "obtain IP automatically" and goes through the normal DORA process — it just always gets the same IP. A static IP bypasses DHCP entirely: the administrator manually enters the IP, mask, gateway, and DNS on the device itself.

10. Which Cisco IOS command shows all currently leased IP addresses along with the MAC addresses of the clients holding them?

A. show ip dhcp pool B. show ip dhcp statistics C. show ip dhcp conflict D. show ip dhcp binding

Correct answer is D. show ip dhcp binding lists every active lease in the DHCP server's database — showing the leased IP address, the client's hardware (MAC) address, the lease expiration time, and whether the binding is automatic or manual. show ip dhcp pool shows pool configuration and available addresses. show ip dhcp statistics shows message counters. show ip dhcp conflict shows addresses removed from the pool due to detected conflicts.

← Back to Home

DHCP – Dynamic Host Configuration Protocol Overview

1. What Is DHCP and Why Is It Used?

2. The DORA Process — How a Client Gets an IP Address

3. DORA — Each Message in Detail

Step 1 — DHCPDISCOVER

Step 2 — DHCPOFFER

Step 3 — DHCPREQUEST

Step 4 — DHCPACK

4. DHCP Lease Time

Lease Renewal Timeline

5. DHCP Scope, Pool, and Exclusions

Key Scope Components

DHCP Exclusions — Why They Matter

Cisco IOS DHCP Server Configuration

6. DHCP Address Bindings and Conflicts

DHCP Conflicts

7. DHCP Relay Agent — ip helper-address

DHCP Relay — How It Works

Configuring ip helper-address

What ip helper-address Forwards

8. DHCP Reservations — Binding a Specific IP to a MAC Address

9. DHCP Snooping — Security Against Rogue DHCP Servers

10. DHCP Troubleshooting and Verification Commands

Client-Side Verification

Cisco Router / Switch Verification

Common DHCP Problems and Solutions

Test Your Knowledge — DHCP Quiz

1. What does the acronym DORA stand for in the context of DHCP?

2. Why does a DHCP client use 0.0.0.0 as the source IP address in the DHCPDISCOVER message?

3. Why is the DHCPREQUEST message sent as a broadcast even though the client already knows which server it wants to use?

4. A DHCP lease has a duration of 8 hours. At what point does the client first attempt to renew the lease, and how does it do so?

5. Why must ip dhcp excluded-address be configured before the DHCP pool on a Cisco router?

6. What is the purpose of the ip helper-address command, and on which interface is it configured?

7. A client receives an IP address of 169.254.47.3 after booting. What does this indicate, and what should be checked first?

8. What is the role of the giaddr field in a relayed DHCP packet, and why is it critical?

9. What is the difference between a DHCP reservation (manual binding) and a statically configured IP address on a host?

10. Which Cisco IOS command shows all currently leased IP addresses along with the MAC addresses of the clients holding them?

5. Why must `ip dhcp excluded-address` be configured before the DHCP pool on a Cisco router?

6. What is the purpose of the `ip helper-address` command, and on which interface is it configured?

8. What is the role of the `giaddr` field in a relayed DHCP packet, and why is it critical?