Essentialy, the server reporting the error contains the record in it`s local table. AD reports that the record does not exist, hence the assumption that i tis corrupt.

 

If this problem occures after reboot it could be orphaned in AD, because AD stops earlier than netlogon should de-register records (just thinking loudly).

 

I`ll try:

Before system reboot manualy stop netlogon, because of his job (de-registering records).

After reboot, launch the dnsmgmt.msc (dns administartion console), expand ‘reverse lookup zones’, find and select appropriate zone. In the right hand window, find and delete record(s) referenced in alarm(s).

Wait till replication process complete successful, stop netlogon and reboot the server. Is there possibility, that another records goes up and would asking for removal.

Start server and check dns events for errors.

 

Hope that this would help you

Regards,

Robert

 

Reply via email to