Dynamic DNS is a feature that allows hosts to register their records in DNS, thus removing the need for administrators to manually create records.
In addition, Secure Dynamic Update can be required for zones that are Active Directory-integrated (and should be required, per best practices), which allows only members of the Authenticated Users group to register records.
Perform a packet capture (wireshark) on the client or the server (easier on the client, less packets) to verify this hypothesis.
If the client is not sending its hostname to the dhcp server, it has no way to update the dns zone.
I'm afraid that you're going to have to approach this from the client end.
Changing the timeouts is only going to help clients the next time they check in, which is usually after half the existing lease time, or sometimes during boot.
When a DHCP server is added to the Dns Update Proxy group, its records aren't secured, meaning that other DHCP servers can update the records.
In additon, hosts can change the records and then become the owner of the record.
However it is successfully giving out IP address to all IP enabled device and machine but when updating the DNS entry, only the Windows machine (workstations and server) gets their IP registered in the DNS server, therefore i cannot ping and access the other Linux machine apart from using IP address only.We have multiple hosts as of late that sucessfully pull a DHCP address and are domain machines that there is no A record being created for the host.I can do a reverse lookup on the IP and that works but not name to IP. Q: Does setting DNS dynamic update credentials on DHCP achieve the same result as adding a DHCP server to the Dns Update Proxy group?A: The short answer is no; however, it's important to step back and understand how DNS interacts with DHCP regarding dynamic updates, then look at what each of the two actions mentioned in the title actually does—namely, setting DNS dynamic update credentials on DHCP and adding a DHCP server to the Dns Update Proxy group.
What this means in practice is the following: This means the DHCP server computer account will own certain records in DNS, such as the PTR records and even some A records for older hosts.