It's possible that the owner was just the existing owner on the tombstoned record.In ADSIEDIT, you can open the Configuration Naming Context, select Partitions, and in the right pane, right-click on the Domain DNSZones partition and select New Connection To Naming Context, then drill-down to Microsoft DNS to view the records for the zone.Some PCs on the other hand appear to register their own 'A' records directly with the DNS server.This results in an 'A' record owned by either 'system' or the PC's AD computer account.1a) Even if these are enabled, you might need to make sure the DHCP server has permissions to update DNS records.If your DHCP server is also a domain controller, then you are probably fine, if not, then you may want to see if the DHCP server is a member of the "Dns Update Proxy" group in AD.
The DHCP servers are configured with the following settings ticked: 'Enable DNS dynamic updates according to the settings below' 'Always dynamically update DNS A and PTR records' 'Discard A and PTR records when a lease is deleted' Some PCs seem to work fine.
I'd really appreciate some advice if anyone has come across this before.
I believe what you are wanting to do is simply tell all your DHCP clients to not register their own DNS records in AD.
I have checked the event viewer logs for the DHCP and DNS server but nothing is present?
The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.
When a client unregisters, the record is marked as dns Tombstoned.