This is not the case with other computers on the network which will cause the DNS to update with any change of IP. I have compared the problematic computer's Host A security settings with another computer's Host A security settings. I matched them up exactly except for giving the respective computers full control of the Host A s. I had this happen in my last environment and made an account called DNSupdate that had the sole purpose of updating DNS.
Windows Client DHCP and DNS Registration - Infoblox Experts Community
I do work closesly with the folks that administer these devices, and have some working knoledge of these devices. I've been fighting a problem for years since we implemented Infoblox in our AD enviroment. From time to time, we would try to connect to a client machine via DNS name and would not have connectivity. We would have to track down the client IP address and connect that way. It's not the same computers every time. It seems to be random. Previously we had TXT records enabled.
Both servers have the same account configured for DNS dynamic update registration. I checked DNS record permissions and everything seems to be all right account for dynamic updates is owner of the record. PTR zone is in place.
Well, I will also offer the nitty gritty below the summary for those who want to read. By default, the ACL gives Create permission to all members of the Authenticated User group, the group of all authenticated computers and users in an Active Directory forest. This means that any authenticated user or computer can create a new object in the zone. Also by default, the creator owns the new object and is given full control of it.