DHCPv6 configuration

By default, the DHCP server is configured by reading the /etc/dhcpv6/dhcpsdv6.cnf file, which specifies the initial database of options and addresses.

The server is started from SRC commands. If dhcpsdv6 is intended to start across reboots, add an entry into the /etc/rc.tcpip file.

Configuring the DHCP server is usually the hardest part of using DHCP in your network. First, decide what networks you want to have DHCP clients on. Each subnet in your network represents a pool of addresses that the DHCP server must add to its database. For example:
subnet dead:dead:aaaa:: 48 {
        option 23 dead::beef beef:aaaa::bbbb:c aaaa:bbbb::cccc  #nameserver list
        option 24 austin.ibm.com ibm.com                        # domain list

The example above shows a subnet, dead:dead:aaaa::, with a prefix of 48 bits. All addresses in this subnet, dead:dead:aaaa::1 through dead:dead:aaaa:ffff:ffff:ffff:ffff:ff7f, are in the pool. Optionally, a range can be specified on the end of the line before the '{' or a range or exclude statement can be included in the subnet container.

Comments begin with a # (pound sign). Text from the initial #, to the end of the line, is ignored by the DHCP server. Each option line is used by the server to tell the client what to do.

If the server does not understand how to parse an option, it uses default methods to send the option to the client. This also allows the DHCP server to send site-specific options that are not RFC defined, but may be used by certain clients or client configurations.