A customer encountered this error message, when he tried to join computer to domain or change the DNS from Primary to AD integrated. Oh did I mention that the 2 out of 3 domain controllers in the domain are offline?

The offline domain controllers have missing SYSVOL and NETLOGON shares. Event viewer is flooded with errors. DCdiag and Netdiag shows the FSMO roles and network is working properly. So it isn’t all that bad.
AD replication is not working properly which means FRS and/or DNS is a problem. The customer told me that the DNS zone was missing and the current zone was recreated manually.as primary. Hmm no good.
Changing the DNS zone type from Primary to AD integrated gives an error replication partition is not created. Creating the default DNS zones (CreateBuiltinDirectoryPartitions) manually using dnscmd gives an error 13.
Recreated DNS as a primary zone and there was this strange entry in the event viewer about cannot access Active Directory and waiting for it to start. There is something disjointed here. It is as if the server has lost its connection to AD.
Reset the only working domain controller password using netdom on the sole working machine is nerve biting but after the reboot the DNS is now magically AD integrated. The syntax for the netdom command is a bit weird. But then is a weird day.
netdom resetpw myserver /userd:myserver\administrator /password:*
Note administrator is a domain admin account.
To get the SYSVOL and NETLOGON back the File Replication Service must be running. on all servers. The only working server have event id 13568 in File Replication. Following Event id article, is to re-generate the the SYSVOL with “Enable Journal Wrap Automatic Restore”. But this is meant to re-replicate from a working DC. I took a chance and followed the suggestion in the event id, and trigger a full sync. It cleared the SYSVOL and recreated successfully.
Create DNS partition, DNS fix link, the SYSVOL fix and here