DHCPv6 limitations - BlueCat Integrity - 9.3.0

Address Manager Administration Guide

Product name
BlueCat Integrity

The following lists limitations of DHCPv6.

  • DHCPv6 runs as separate instance—when DHCPv6 and DHCPv4 are enabled, you will have two instances of DHCP, each with their own configuration and leases file.
  • DHCPv6 prefix delegation isn't directly supported by Address Manager, however you can implement DHCPv6 prefix delegation as a Raw option. Contact BlueCat Customer Care for assistance.
  • The following limitations arise from the ISC DHCP implementation:
    • IPv6 addresses that fall into DHCPv6 ranges between ::80 and ::FF with any network prefix can't be leased.
    • DHCPv6 server can only communicate with a DNS server over IPv4 for DDNS updates.
    • Depending on your DDNS configuration between a managed DHCPv6 server and an external DNS server, the IPv6 address lease process time can take up to 7 minutes. To enable DDNS updates on the DHCPv6 server, you need to specify the IP address of the DNS server along with other necessary options. This limitation only occurs when you specify the IP address of the DNS server in the /etc/resolv.conf file and there's no IPv6 reverse-lookup zone created on the DNS server. To avoid this limitation, you MUST create an IPv6 reverse-lookup zone on the DNS server through the Address Manager user interface. You can also use the DHCPv6 RAW option, in the Address Manager user interface, to specify the IP address of the DNS server. This is the recommended practice for now to enable DDNS between the DHCPv6 server and the DNS server. Use the following RAW option:
      zone <reverse zone name> {primary <IPv4 address of DNS server>;}