By default, secure dynamic update prevents a client from creating, deleting, or modifying a record if the client is not the original creator of the record.
For example, if two computers have the same name and both try to register their names in DNS, dynamic update fails for the client that registers second.
I can do a reverse lookup on the IP and that works but not name to IP.
The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.
Cause: The client was not able to register with the DNS server because of intermittent problems with either the DNS server or the network.
Solution: At the client computer, use the ipconfig command as appropriate to retry registration or renewal and update client information with the DNS server.
You can use the ipconfig /registerdns command option to manually force a retry of the client computer's dynamic registration.
Are there any issues with only clients registering in DNS for themselves?To check, right-click your DHCP scope and go to properties.On the DNS tab enable DNS dynamic updates and set to "Always dynamically update..." Also enable Dynamic Update for clients that do not request updates.1a) Even if these are enabled, you might need to make sure the DHCP server has permissions to update DNS records.If your DHCP server is also a domain controller, then you are probably fine, if not, then you may want to see if the DHCP server is a member of the "Dns Update Proxy" group in AD.