DHCP does much more than assign an IPv4 address.
A DHCP server can also tell a client:
- Which subnet mask to use
- Where the default gateway is
- Which DNS servers to query
- Which DNS domain belongs to the network
- How long the address lease is valid
- Which DHCP server supplied the configuration
- Which boot server or boot file may be required
- Which vendor-specific information applies to a particular type of device
These additional values are carried using:
DHCP Options
RFC 2132 defines many of the commonly used DHCP options and describes DHCP options as tagged configuration data carried inside the DHCP message.

How DHCP Options Work
The DHCP message contains an options area where configuration parameters can be carried using a structured format.
Conceptually:
DHCP Message
|
+-- Message Type
+-- Client / Server Information
+-- Assigned Address
|
+-- DHCP Options
|
+-- Option 1
+-- Option 3
+-- Option 6
+-- Option 15
+-- Option 51
+-- Option 54
+-- Other Options
Different DHCP messages contain different combinations of options.
For example:
DHCPDISCOVER
may contain options describing what the client wants.
DHCPOFFER
may contain the address and configuration the server is prepared to provide.
DHCPREQUEST
may identify the requested address and selected server.
DHCPACK
can contain the final configuration the client should use.
DHCP Message Type — Option 53
Although this article focuses on other commonly encountered options, one option is essential for understanding packet captures:
Option 53 — DHCP Message Type
It identifies messages such as:
- DHCPDISCOVER
- DHCPOFFER
- DHCPREQUEST
- DHCPACK
- DHCPNAK
- DHCPDECLINE
- DHCPRELEASE
- DHCPINFORM
When analyzing DHCP in Wireshark, Option 53 is often one of the first values to inspect.
Core Client Configuration Options
Several DHCP options directly define normal IPv4 network configuration.
Option 1 — Subnet Mask
DHCP Option 1 provides the IPv4 subnet mask.
Example:
Option 1 — Subnet Mask
255.255.255.0
The client can combine this with its assigned IPv4 address.
For example:
IP Address:
192.168.10.50
Subnet Mask:
255.255.255.0
Resulting Network:
192.168.10.0/24
Without the correct subnet mask, the client may incorrectly determine whether a destination is:
- Local
- Remote
- Reachable directly
- Reachable through a router
Option 3 — Router / Default Gateway
Option 3 provides one or more router addresses.
For most endpoint networks, the first relevant router is used as the client’s default gateway.
Example:
Option 3 — Router
192.168.10.1
The resulting client configuration might be:
IP Address:
192.168.10.50
Subnet Mask:
255.255.255.0
Default Gateway:
192.168.10.1
A wrong Option 3 value can create a common symptom:
The client receives an IP address but cannot reach remote networks.
Option 6 — Domain Name Server
Option 6 provides DNS resolver addresses.
Example:
Option 6 — DNS Servers
192.168.10.10
192.168.10.11
The client may then use those resolvers for DNS queries.
A client can therefore have a perfectly valid:
- IP address
- Subnet mask
- Gateway
but still appear to have an Internet or application problem if Option 6 provides an incorrect DNS server.
Option 15 — Domain Name
Option 15 supplies a DNS domain name.
Example:
Option 15 — Domain Name
corp.example.com
This can become part of the client’s DNS configuration.
Option 15 should not be confused with the DNS server addresses themselves.

Option 51 — IP Address Lease Time
Option 51 tells the client how long the assigned address lease is valid.
RFC 2132 specifies the lease time in seconds.
Example:
Option 51:
28800 Seconds
Equivalent:
8 Hours
The lease lifetime works together with:
- T1 — Renewal
- T2 — Rebinding
- Lease expiration
The client does not normally assume that the assigned address belongs to it permanently.
Option 54 — DHCP Server Identifier
Option 54 identifies a DHCP server involved in the transaction.
For example:
Option 54 — Server Identifier
192.168.10.5
This becomes especially important if multiple DHCP servers respond to the same DHCPDISCOVER.
Imagine:
Server A:
192.168.10.5
Server B:
192.168.10.6
The client might receive multiple offers.
The Server Identifier helps distinguish which server sent each offer and allows the client to identify the selected DHCP server during the appropriate DHCPREQUEST exchange.
Vendor-Specific DHCP Options
Enterprise networks frequently need to provide different DHCP information to different device types.
Examples include:
- Wireless access points
- IP phones
- PXE boot clients
- Specialized appliances
- Zero-touch deployment devices
- Vendor-managed network equipment
Two particularly important options are:
Option 60 — Vendor Class Identifier
and
Option 43 — Vendor-Specific Information
These options can work together.
Option 60 — Vendor Class Identifier
Option 60 allows a DHCP client to identify the type or class of device it represents.
RFC 2132 defines Option 60 as the Vendor Class Identifier. A DHCP server that understands the class can use it when deciding what vendor-specific information to return.
Conceptually:
Option 60:
Vendor Class Identifier:
ExampleVendor-AP
The server can then apply a class-specific policy.
Conceptually:
Client
|
| Option 60:
| "ExampleVendor-AP"
v
DHCP Server
|
| Match Vendor Class
v
Return Appropriate Vendor Information
Option 43 — Vendor-Specific Information
Option 43 carries:
Vendor-Specific Information
RFC 2132 defines Option 43 as a container for vendor-specific information and allows vendor-defined sub-options inside it.
A server might first identify the client using Option 60 and then return vendor-specific information using Option 43.
Conceptually:
Client → DHCP Server
Option 60:
"I am Vendor Device Type X"
DHCP Server → Client
Option 43:
"Here is configuration specifically for Device Type X"
Real-World Example — Wireless Access Points
A common enterprise use case is wireless access-point controller discovery.
Cisco documents the use of Option 60 and Option 43 with lightweight access points. The AP’s Vendor Class Identifier allows the DHCP server to distinguish the AP type and return appropriately formatted Option 43 information.
Conceptually:
Client Device:
Wireless Access Point
Option 60:
Vendor Class Identifier
DHCP Server:
Matches AP Class
Option 43:
Controller Discovery Information
The exact Option 43 format is vendor-specific.
It should not be assumed that an Option 43 value designed for one vendor will work for another.

DHCP Options 66 and 67 for Network Boot
DHCP is also commonly involved in:
PXE — Preboot Execution Environment
PXE allows a device to boot using resources delivered over the network rather than relying only on a local operating system.
Two frequently encountered DHCP options are:
- Option 66 — TFTP Server Name / Boot Server Host Name
- Option 67 — Bootfile Name
Option 66 — Boot Server Host Name
Option 66 can provide the name or address information associated with a network boot server.
Example:
Option 66:
10.10.10.20
or, depending on the environment:
Option 66:
pxe.example.com
Option 67 — Bootfile Name
Option 67 identifies a boot file.
Example:
Option 67:
bootx64.efi
A simplified boot process can therefore look like:
PXE Client
|
| DHCP
v
Receives IP Configuration
|
+-- Boot Server Information
+-- Boot File Information
|
v
Boot Service / TFTP
|
v
Download Boot Program
Option 60 and PXE
Option 60 can also appear in PXE-related environments because PXE clients can identify themselves through a vendor class.
However, PXE deployments should not be simplified into:
“Always configure Options 60, 66 and 67 on the DHCP server.”
Microsoft specifically documents scenarios where configuring DHCP Options 60, 66 and 67 globally can cause PXE boot failures, particularly where DHCP and PXE services are on separate systems. Microsoft recommends using the appropriate network forwarding/helper design for those environments rather than assuming those options should always be configured on DHCP.
PXE Architecture Example
A deployment may contain:
DHCP Server:
10.10.10.10
PXE / Boot Server:
10.10.20.20
Client VLAN:
192.168.50.0/24
Layer 3 Gateway:
192.168.50.1
The network may need DHCP/PXE traffic forwarding toward both required services depending on the deployment.
Microsoft notes that a PXE environment requires a DHCP server or proxy DHCP service as well as a PXE/TFTP infrastructure for network boot.

Option 82 — Relay Agent Information
Option 82 is different from the client-oriented options described above.
It is called:
DHCP Relay Agent Information Option
RFC 3046 defines Option 82 as information inserted by a DHCP relay agent when forwarding client-originated DHCP traffic toward a server.
It can provide information about where the DHCP request entered the network.
Common Option 82 Sub-Options
Two important sub-options are:
- Circuit ID
- Remote ID
Circuit ID
Circuit ID may identify information associated with the client’s attachment circuit.
Examples can include:
- Switch port
- Router interface
- Access circuit
- VLAN-related information
- Other locally meaningful circuit identifiers
RFC 3046 specifically describes Circuit ID as an agent-local identifier for the incoming circuit and lists examples such as interface or switch-port identifiers.
Remote ID
Remote ID can identify information associated with the remote endpoint or access system.
The exact value depends on the implementation.
Example
Conceptually:
Option 82
Circuit ID:
VLAN20-GigabitEthernet1/0/10
Remote ID:
Access-Switch-01
The DHCP server can use this information for:
- Address-assignment policies
- Subscriber identification
- Access control
- Troubleshooting
- Logging
- Security enforcement
Who Adds Option 82?
A critical point:
The client normally does not create Option 82.
The relay infrastructure inserts it.
A simplified flow is:
DHCP Client
|
| DHCPDISCOVER
v
DHCP Relay
|
| Add Option 82
v
DHCP Server
RFC 3046 requires supporting DHCP servers to echo recognized relay-agent information back toward the relay, which then removes its Option 82 information before forwarding the response to the client.

Packet Analysis and Troubleshooting
Wireshark makes DHCP options much easier to understand because the options are decoded individually.
Wireshark Filter
A useful DHCP display filter is:
dhcp
You can also inspect DHCPv4 traffic using:
udp.port == 67 || udp.port == 68
Linux tcpdump
Capture DHCP traffic:
sudo tcpdump -nn -i any 'udp port 67 or udp port 68'
For more detail:
sudo tcpdump -nn -vvv -i any 'udp port 67 or udp port 68'
Example DHCPACK
A simplified DHCPACK might contain:
DHCP Message Type:
ACK
Assigned Address:
192.168.10.50
Option 1:
255.255.255.0
Option 3:
192.168.10.1
Option 6:
192.168.10.10
192.168.10.11
Option 15:
corp.example.com
Option 51:
28800 seconds
Option 54:
192.168.10.5
The client now has enough information to configure:
IP:
192.168.10.50
Mask:
255.255.255.0
Gateway:
192.168.10.1
DNS:
192.168.10.10
192.168.10.11
Domain:
corp.example.com
Lease:
8 Hours
Troubleshooting by Option
A useful troubleshooting approach is to separate:
Address assignment
from:
Option assignment
A client receiving an IP address does not prove that every DHCP option is correct.
Client Gets IP but Cannot Reach Other Networks
Verify:
Option 3
Example problem:
Correct Gateway:
192.168.10.1
DHCP Option 3:
192.168.10.254
The DHCP lease succeeds, but routing may fail.
Client Gets IP but DNS Does Not Work
Verify:
Option 6
Check whether the supplied DNS resolver:
- Exists
- Is reachable
- Is listening
- Can resolve the required zones
Wrong DNS Suffix
Verify:
Option 15
A wrong domain value can affect:
- Name resolution behavior
- Search suffix use
- Enterprise application access
Vendor Device Does Not Discover Controller
Check:
- Option 60 value sent by client
- DHCP class matching
- Option 43 format
- Hexadecimal encoding where required
- Device/vendor documentation
- DHCP scope or policy configuration
Cisco’s Option 43 guidance demonstrates that vendor class matching and exact Option 43 formatting matter for controller discovery.
PXE Client Gets IP but Does Not Boot
Check:
- DHCP response
- PXE server reachability
- Relay / helper configuration
- Option 60 handling
- Boot server discovery
- Boot file selection
- Option 66 where applicable
- Option 67 where applicable
- UEFI vs legacy architecture
- TFTP or other boot-transfer service
Do not assume an IP lease means the entire PXE process succeeded.
Option 82 Problems
Inspect:
- Is Option 82 being inserted?
- Which device inserts it?
- Circuit ID value
- Remote ID value
- Whether the DHCP server trusts the relay
- Whether the server has Option 82 policies
- Whether the relay removes the option on return traffic
- DHCP snooping interactions

DHCP Options Quick Reference
| Option | Name | Typical Purpose |
|---|---|---|
| 1 | Subnet Mask | Defines IPv4 subnet mask |
| 3 | Router | Provides default gateway/router |
| 6 | Domain Name Server | Provides DNS resolver addresses |
| 15 | Domain Name | Provides DNS domain name |
| 43 | Vendor-Specific Information | Carries vendor-defined configuration |
| 51 | IP Address Lease Time | Defines DHCP lease duration |
| 54 | Server Identifier | Identifies DHCP server |
| 60 | Vendor Class Identifier | Identifies device/vendor class |
| 66 | TFTP Server Name | Can identify network boot server |
| 67 | Bootfile Name | Identifies network boot file |
| 82 | Relay Agent Information | Carries relay/access-circuit information |
Key Takeaways
- DHCP options allow DHCP to provide much more than an IPv4 address.
- Option 1 provides the subnet mask.
- Option 3 provides router/default-gateway information.
- Option 6 provides DNS resolver addresses.
- Option 15 provides the DNS domain name.
- Option 51 defines the IP-address lease duration.
- Option 54 identifies the DHCP server involved in the exchange.
- Option 60 identifies a vendor or client class and can be used by the server for policy matching.
- Option 43 carries vendor-specific information whose meaning and format depend on the vendor. RFC 2132 specifically allows vendor-defined information within this option.
- Options 60 and 43 are commonly associated with vendor-aware device provisioning.
- Options 66 and 67 are commonly encountered in network-boot environments, but they should not be treated as a universal PXE configuration method. Microsoft explicitly warns that blindly configuring Options 60, 66 and 67 can cause PXE failures in some architectures.
- Option 82 is different because it is normally inserted by DHCP relay infrastructure rather than by an ordinary endpoint.
- Circuit ID and Remote ID are common Option 82 sub-options.
- Receiving a valid IP address does not prove that the DHCP options are correct.
- When troubleshooting, inspect the actual options carried in DHCPOFFER and DHCPACK rather than assuming the problem is DHCP address assignment.
DHCP options transform DHCP from a simple address-allocation protocol into a flexible network configuration and provisioning system.
A normal workstation may only require:
Option 1
Option 3
Option 6
Option 15
Option 51
while a specialized enterprise device might additionally depend on:
Option 43
Option 60
A network-boot environment may involve:
Option 60
Option 66
Option 67
and an access or relay network may use:
Option 82
Understanding what each option actually means makes DHCP packet captures easier to read and helps separate:
- Address-allocation problems
- Routing problems
- DNS problems
- Vendor-provisioning problems
- PXE problems
- Relay-policy problems
That distinction is one of the most important skills in practical DHCP troubleshooting.
Useful Links and References
SanchitGurukul Resources
Official Technical References
Your feedback matters
Was this post helpful?
Discussion
0 approved comments
No approved comments yet. You can start the discussion below.
Leave a Comment
No login is required. Name and email are used for moderation/security. Your email is never displayed publicly. All comments require administrator approval.
Discover more from SanchitGurukul
Subscribe to get the latest posts sent to your email.
