After further investigation and looking into our issue. I discovered this article that sum's up our issue. and also provided the fix we needed.
To fix the issue, we basicaly used the Option 2 that is disribed
/quote
- In AD, create and configure a dedicated Domain User account to use as credentials in DHCP. The user account does not need any elevated rights, a normal user account is fine, however I recommend using a Strong non-expiring password on the account.
- In the DHCP Console, in Windows 2003, select the DHCP server properties or in Windows 2008 and 2008 R2, select Scope properties , select the Advanced tab, click the Credentials button, and provide the account's credentials.
- If using Windows 2000, it must be done with the Netsh command. Windows 2003 and newer can also be done with the Netsh command, if you desire
/end quote
This way all DNS Host A records belong to the account and can be updates, deleted by the DHCP Server or Servers...
Corvax