DHCP options
DHCP uses the same message format as BOOTP, but DHCP uses the Option field to carry information for
dynamic address allocation and to provide additional configuration information to clients.
Figure 19 DHCP option format
Common DHCP options
The following are common DHCP options:
Option 3—Router option. This option specifies the gateway address.
•
Option 6—DNS server option. This option specifies the DNS server's IP address.
•
Option 33—Static route option. This option specifies a list of classful static routes (the destination
•
addresses in these static routes are classful) that a client should add into its routing table. If both
Option 33 and Option 121 exist, Option 33 is ignored.
Option 51—IP address lease option.
•
Option 53—DHCP message type option. This option identifies the type of the DHCP message.
•
Option 55—Parameter request list option. This option is used by a DHCP client to request specified
•
configuration parameters. The option contains values that correspond to the parameters requested
by the client.
Option 60—Vendor class identifier option. It is used by a DHCP client to identify its vendor, and by
•
a DHCP server to distinguish DHCP clients by vendor class and assign specific IP addresses for the
DHCP clients.
•
Option 66—TFTP server name option. This option specifies a TFTP server to be assigned to the
client.
Option 67—Bootfile name option. This option specifies the bootfile name to be assigned to the
•
client.
Option 121—Classless route option. This option specifies a list of classless static routes (the
•
destination addresses in these static routes are classless) that the requesting client should add to its
routing table. If both Option 33 and Option 121 exist, Option 33 is ignored.
Option 150—TFTP server IP address option. This option specifies the TFTP server IP address to be
•
assigned to the client.
For more information about DHCP options, see RFC 2132 and RFC 3442.
Custom DHCP options
Some options, such as Option 43, Option 82, and Option 184, have no standard definitions in RFC
2132.
32