Dhcp clients not updating reverse dns
The basic crux of the issue is that MS DNS uses Kerberos for authentication to update DNS records, while ISC DHCP, out of the box, supports TSIG [for BIND].
The scripts above are rather lengthy, so I won't post them here, but the basic steps are: Generate a keytab using ktutil.
Its cooperation is based on DHCP server asking to add the DHCP clients in DNS zones.
For instance, your client called then the leased IP address is returned, and reverse resolution also returns as expected.
So, we decided to fix these things when a slot of time was available, so I was able to finish the proper implementation with this shiny features: The latter feature is a very neat one.I do not understand what I need to check, as I have never had this problem. This page describes using and configuring DHCP for IPv4 (DHCPv4) and IPv6 (DHCPv6) to enable automatic updating of both the forward and reverse mapping zone file.For domain-joined clients, they will have an A record registered in the forward lookup zone, but not the reverse lookup zone. This can be completed through triggers for ISC DHCP.The IPv4-only script and setup information is available from ISC DHCPd: Dynamic DNS updates against secure Microsoft DNS There is an alternative script that supports IPv4 and IPv6, but using the same premise as the above script is available at