DNS and AD replication issues - need help!

[bludbunny]

Hi guys

I have been having a problem for a while now with DNS replication - this has now spread to active directory. I am running 3 W2Ks DC's / mixed mode, with the third server running Proxy 2.0 client with our mail server (Mdaemon)

The problem is that with this DNS / AD replication issue, new computers/users added to the domain have problems logging on sometimes - ie. no username found / no computer account in the domain etc. In other words replication is not occurring.

The errors I am getting on my servers are:
1. Netlogon - event id: 5781 - Dynamic registration or deregistration of one or more DNS records failed.....
2. NTDS replication - event ID: 1586 - The checkpoint with the PDC was unsuccessful..... DNS problems etc etc.

I have recenlty had the problem where my first server could not run any active directory MMC's - fixed by removing proxy 2.0 client. Since that, the DNS has not been acting right on that server (which is the primary server)

IS there a way to remove and reinstall DNS on the server - would this rectify the problem?

any help would be greatly appreciated,

Brett

 

[billieT]

well, if you're happy to blow away your current DNS, of course you can remove and reinstall it. Control Panel->Add/Remove Programs->Add/Remove Windows Programs... where-ever the DNS is (under Network Services?), deselect it to uninstall it.

OK, after rebooting the box, and blowing your DNS away, reinstall DNS using the same method. When setting up your "new" zone, select Active-Directory Integrated, since that really does work well. Make sure that your server with DNS is pointing to ITSELF as the primary DNS server. Make sure that your other DCs are using that server as their primary DNS as well. Under the computer name settings, make sure that all the servers' (and clients') primary DNS name suffixes are correct, if you're autoregistering them in DNS.

Also, why are you running in Mixed Mode? If you don't have any NT BDCs in your domain - you only have Win2K and above domain controllers - it is totally unnecessary.

Finally, are all your FSMO roles on the same box? and is this the same as the DNS server (it shouldn't be a problem)? Do you only have a single domain in your environment?

 

[bludbunny]

Thanks for the response

I have been through all of the troubleshooting you mention - except for wiping the dns. I did manage to find (somehow) this article below - which all made sense after I read it as the problems started after I upgraded to spack4 on my domain controllers:

http://support.microsoft.com/default.aspx?scid=kb;en-us;300684

After adding the reg. "hack" all is now good.

cheers,
Brett