In an environment running the ISC DHCP server and BIND DNS server, DHCP leases should update the DNS server dynamically with the name and IP address of the client assigned the lease.

This was not working for my Solaris 11.3 clients in my lab.  I tracked this down to the Solaris DHCP client not sending a hostname with its DHCP request.  It is perhaps the case that environments that use DHCP with Solaris might usually configure the client and MAC address in the DHCP server, in which case sending a hostname from the client to the server is not required.

However, in my lab environment, I need the dynamic DNS to work as might normally be expected—the client sends its hostname with the DHCP request so that the DHCP server can register a dynamic update with BIND.  To make this change, remove the interface and add it back with the hostname options:

ipadm delete-addr -r net0/v4
ipadm create-addr -T dhcp -h $(hostname) net0/v4

Once you make this change, you can see the difference in the output of the ISC DHCP server if you are running it with the -d option:

/usr/lib/inet/dhcpd -4 --no-pid -d -cf /etc/inet/dhcpd4.conf -lf /var/db/isc-dhcp/dhcpd4.leases

...
DHCPREQUEST for 10.10.10.103 from 02:08:20:f5:bf:ee via net0
DHCPACK on 10.10.10.103 to 02:08:20:f5:bf:ee via net0
DHCPRELEASE of 10.10.10.103 from 02:08:20:f5:bf:ee via net0 (found)
DHCPDISCOVER from 02:08:20:f5:bf:ee via net0
DHCPOFFER on 10.10.10.103 to 02:08:20:f5:bf:ee (client2) via net0
DHCPREQUEST for 10.10.10.103 (10.10.10.10) from 02:08:20:f5:bf:ee (client2) via net0
DHCPACK on 10.10.10.103 to 02:08:20:f5:bf:ee (client2) via net0
Added new forward map from client2.pg.org. to 10.10.10.103

The last statement above, Added new forward map indicates that the DHCP server is making a dynamic name change in BIND.