Both domain controllers rebooted - problems with DNS

hi

we working on procedure restoring our systems further having powercut extends beyond support of our ups.  we have 2 domain controllers

dc1 (physical) - dns, dhcp. have configured server (bios) boot automatically when power restored. 

dc2 (virtual) - dns. when esx host boots (also boots automatically), server set boot first automatically.

each servers primary dns set point @ other. 

we trying point if experience powercut lasts few hours out of hours, once power restored , dc1 , dc2 have booted, providing automatic services have started, not need manually intervene , both dc's operational.

at moment, when test process rebooting both dc's out of hours, after 10 minutes having restart dns service unable ping servers hostname , both dc's cannot see each other. 

should happen?

hi, if have understanding, doing these tests on test environments.

so did export of virtual dc. right?

i saying because long dcs starting , netlogon services running, not have dns problem. if after (10 mins in case) service stop, have active directory problem. showing problem replication , common case usn rollback has been set 4 windows => incorrect restore procedure.

hkey_local_machine\system\currentcontrolset\services\ntds\parameters\dsa not writable”=dword:00000004

https://support.microsoft.com/en-us/kb/2023007

you can run command confirm: repadmin /options

if see disabled repl, can use procedure. !!! warning !!!!, use on test environment. not in production environment. in production, use microsoft 2023007 kb.

https://exchangeserverpro.com/recovering-a-single-domain-controller-from-a-usn-rollback/

if repl ok , netlogon ok, dns must run. in other case, find here after dns start options:

https://support.microsoft.com/en-us/kb/198408

Windows Server  >  Directory Services