If you’re an experienced Windows system engineer, they may seem a little trivial.
Then I deleted all entries and restarted all the machines (of course I set the lease time to 1 day, one day prior to do the deletion).
It fixed the forward DNS entries for the most part.
Active Directory/DNS is running on Server 2012 R2 in 2012 R2 forest/domain functional levels.
DNS forward and reverse lookup zones accept secure dynamic updates only.
I've been unsuccessful at finding a guide on how to integrate just ISC DHCP into an AD DNS environment.
The configuration file is below, but what I've noted when using ISC DHCP is that non-domain joined clients will not have an A record registered for them in forward/reverse lookup zones.
So please select also “Store the zone in Active Directory”. In a pure Windows Server DNS environment you should select “Allow only secure dynamic updates” otherwise you should select “Do not allow dynamic updates”.
In our case we select “Primary zone” and we want to store the information in Active Directory. Now you have to set Dynamic Update for DNS entry’s.
I just manually deleted any old entries that were not uptodate. I have triple entries on the same IP and all 3 entries are wrong (they don't match the forward at all).