Hello, We have started to have lookup problems in out network.
When a new client gets an IP address, DHCP doesn't update DNS with the record. The DHCP and DNS are on the same box (which is also the primary DC).
When a client unregisters, the record is marked as dns Tombstoned.
The record still exists, but is not visible in DNS Manager.
This would then allow it to delete/modify any 'A' record, even those it has not created.
On the DNS tab enable DNS dynamic updates and set to "Always dynamically update..." Also enable Dynamic Update for clients that do not request updates.Dynamic updates are enabled for both the forward and reverse zones. This could be due to a couple of different things: 1) Are your clients obtaining IPs via a Windows DHCP Server?If so, your DHCP server may not be configured to auto-register their IP with the DNS server.Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).If they are in the forward zone but not the reverse, then something else is going on...However, the reverse DNS entries ("PTR" Records) are not.