I have a question about some behavior I am seeing in my DHCP scopes. This relates to the option to have DHCP "Always dynamically update DNS records".
I have done a lot of work to have all our DHCP distributed addresses registered solely by the DHCP server using a Service Account. What I have found is that when I have this configured, the DHCP server will use the service account to register the DNS record, and the service account shows as the owner of the record. However, almost immediately the lease will get deleted by the client and then recreated by the client itself.
For example my DHCP server is 10.0.0.74, the client gets assigned 10.0.0.201. I can see in the logs that the DHCP server creates the DNS record (created by 10.0.0.74) , then it is immediately deleted and replaced by the client machine (10.0.0.201).
I did have an image to put here to make it clearer, but I get a message stating that I can't post an image until my account is verified.
The only way I have been able to stop this happening is to create a group policy which turns off DNS Dynamic update on the client.
In all the reading about setting up DHCP and a proxy account I have never come across the requirement to apply a group policy setting to stop the client from registering itself.
Is this expected behavior? Have I configured something wrong?
I sort of expected that the DHCP setting I mentioned above would not only register the DNS record for the client, but would make it so the client never registers its own address, but that is clearly not what is happening.
Thanks for any feedback.