DHCP Dynamic DNS is randomly not updating records. DHCP log will show many failures (31), DNS debug log shows very little but many (noerror).
Setup is 2 2008R2 DC's (DC1, DC2) in a cluster (I know, I know) running DHCP as a clustered service. DNS is AD integrated and DC1 is the primary DNS for all nodes via DHCP and static entries. I recently setup credentials for DHCP dynamic updates that was not existing before, I added the two DC's to the DNSUpdateProxy group and ran the following command: dnscmd /config /OpenAclOnProxyUpdates 0.
DNS log will show failed updates even though it DNS appears to have an updated entry. Scavenging is not currently enabled. Secure and nonsecure are enabled on the forward zone, but only some reverse zones. Previous to me there was a general 10.0.0.0/8 reverse zone allowing secure and nonsecure updates but also the appropriate 10.x.x.0/24 reverse zone but not allowing any updates. I'm not seeing failures but will my DHCP DNS renewals fail because of the reverse DNS? I also have some DHCP entries that do not leave the pending state.
My question is why aren't all my records updating their forward records? And what's the benefit or disadvantage or using a large reverse DNS lookup zone?
Thanks in advance