Currently we have 2 Domain Controllers serving 1 domain in 2 locations. Location 2 had a DC failure several months ago. I cleaned up all metadata regarding the old DC and promoted a new DC.
The new DC at location 2 replicates from the existing DC at location 1 fine, but the existing DC at location 1 will not replicate from the new DC at location 2.
New DC: jmac-dc
Existing DC: hexom-app1
Here is the DCDIAG DNS test when ran on the existing DC:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = hexom-app1
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\HEXOM-APP1
Starting test: Connectivity
......................... HEXOM-APP1 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\HEXOM-APP1
Starting test: Replications
[Replications Check,HEXOM-APP1] A recent replication attempt failed:
From JMAC-DC to HEXOM-APP1
Naming Context: DC=DomainDnsZones,DC=hexom,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2014-09-18 13:59:27.
The last success occurred at 2014-03-01 06:19:22.
8700 failures have occurred since the last success.
[JMAC-DC] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
The source remains down. Please check the machine.
[Replications Check,HEXOM-APP1] A recent replication attempt failed:
From JMAC-DC to HEXOM-APP1
Naming Context: DC=ForestDnsZones,DC=hexom,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2014-09-18 14:00:22.
The last success occurred at 2014-03-01 05:45:46.
5643 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,HEXOM-APP1] A recent replication attempt failed:
From JMAC-DC to HEXOM-APP1
Naming Context: CN=Schema,CN=Configuration,DC=hexom,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2014-09-18 13:58:38.
The last success occurred at 2014-03-01 05:45:46.
5528 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,HEXOM-APP1] A recent replication attempt failed:
From JMAC-DC to HEXOM-APP1
Naming Context: CN=Configuration,DC=hexom,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2014-09-18 13:48:44.
The last success occurred at 2014-03-01 05:45:46.
4938 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,HEXOM-APP1] A recent replication attempt failed:
From JMAC-DC to HEXOM-APP1
Naming Context: DC=hexom,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2014-09-18 13:59:58.
The last success occurred at 2014-05-30 16:20:37.
6355 failures have occurred since the last success.
The source remains down. Please check the machine.
......................... HEXOM-APP1 failed test Replications
Running partition tests on : DomainDnsZones
Running partition tests on : ForestDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : hexom
Running enterprise tests on : hexom.local
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = hexom-app1
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\HEXOM-APP1
Starting test: Connectivity
......................... HEXOM-APP1 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\HEXOM-APP1
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... HEXOM-APP1 passed test DNS
Running partition tests on : DomainDnsZones
Running partition tests on : ForestDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : hexom
Running enterprise tests on : hexom.local
Starting test: DNS
Test results for domain controllers:
DC: hexom-app1.hexom.local
Domain: hexom.local
TEST: Basic (Basc)
Warning: adapter
[00000006] Microsoft Virtual Machine Bus Network Adapter has
invalid DNS server: 10.0.0.3 (jmac-dc.hexom.local.)
Warning: The AAAA record for this DC was not found
TEST: Forwarders/Root hints (Forw)
Error: Forwarders list has invalid forwarder: 10.0.0.3 (jmac-dc.hexom.local.)
TEST: Delegations (Del)
Error: DNS server: jmac-dc.hexom.local. IP:10.0.0.3
[Broken delegated domain _msdcs.hexom.local.]
TEST: Records registration (RReg)
Network Adapter
[00000006] Microsoft Virtual Machine Bus Network Adapter:
Warning:
Missing AAAA record at DNS server 10.0.1.8:
hexom-app1.hexom.local
Warning:
Missing AAAA record at DNS server 10.0.1.8:
gc._msdcs.hexom.local
Warning: Record Registrations not found in some network adapters
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 10.0.0.3 (jmac-dc.hexom.local.)
3 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 10.0.0.3 Name resolution is not functional. _ldap._tcp.hexom.local. failed on the DNS server 10.0.0.3
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: hexom.local
hexom-app1 PASS WARN FAIL FAIL PASS WARN n/a
......................... hexom.local failed test DNS