Domain Replication between Parent & Child

[jase1871]

#155425

Hi All, i have been experiencing some issues with my server unable to replicate the event log is filled with issues: i ran dcdiag and got the following result:

Directory Server Diagnosis

Performing initial setup:
Trying to find home server…
Home Server = LiveDC
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Head-OfficeLiveDC
Starting test: Connectivity
……………………. LiveDC passed test Connectivity

Doing primary tests

Testing server: Head-OfficeLiveDC
Starting test: Advertising
……………………. LiveDC passed test Advertising
Starting test: FrsEvent
……………………. LiveDC passed test FrsEvent
Starting test: DFSREvent
……………………. LiveDC passed test DFSREvent
Starting test: SysVolCheck
……………………. LiveDC passed test SysVolCheck
Starting test: KccEvent
……………………. LiveDC passed test KccEvent
Starting test: KnowsOfRoleHolders
……………………. LiveDC passed test KnowsOfRoleHolders
Starting test: MachineAccount
……………………. LiveDC passed test MachineAccount
Starting test: NCSecDesc
……………………. LiveDC passed test NCSecDesc
Starting test: NetLogons
……………………. LiveDC passed test NetLogons
Starting test: ObjectsReplicated
……………………. LiveDC passed test ObjectsReplicated
Starting test: Replications
[Replications Check,LiveDC] A recent replication attempt failed:
From BRIDGENDDC to LiveDC
Naming Context: DC=ForestDnsZones,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:37.
6 failures have occurred since the last success.
The guid-based DNS name
7c485ada-9e08-4904-8f99-67184db3ed5a._msdcs.transport.local
is not registered on one or more DNS servers.
[Replications Check,LiveDC] A recent replication attempt failed:
From SOUTHAMPTONDC to LiveDC
Naming Context: DC=ForestDnsZones,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:37.
6 failures have occurred since the last success.
The guid-based DNS name
11083fce-735e-425e-8a60-651d1f84a207._msdcs.transport.local
is not registered on one or more DNS servers.
[Replications Check,LiveDC] A recent replication attempt failed:
From MANCHESTERDC to LiveDC
Naming Context: DC=ForestDnsZones,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:37.
6 failures have occurred since the last success.
The guid-based DNS name
dad67b59-087c-40a2-a2fb-21bb3bd82457._msdcs.transport.local
is not registered on one or more DNS servers.
[Replications Check,LiveDC] A recent replication attempt failed:
From BRIDGENDDC to LiveDC
Naming Context:
CN=Schema,CN=Configuration,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:37.
9 failures have occurred since the last success.
The guid-based DNS name
7c485ada-9e08-4904-8f99-67184db3ed5a._msdcs.transport.local
is not registered on one or more DNS servers.
[Replications Check,LiveDC] A recent replication attempt failed:
From SOUTHAMPTONDC to LiveDC
Naming Context:
CN=Schema,CN=Configuration,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:37.
9 failures have occurred since the last success.
The guid-based DNS name
11083fce-735e-425e-8a60-651d1f84a207._msdcs.transport.local
is not registered on one or more DNS servers.
[Replications Check,LiveDC] A recent replication attempt failed:
From MANCHESTERDC to LiveDC
Naming Context:
CN=Schema,CN=Configuration,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:37.
9 failures have occurred since the last success.
The guid-based DNS name
dad67b59-087c-40a2-a2fb-21bb3bd82457._msdcs.transport.local
is not registered on one or more DNS servers.
[Replications Check,LiveDC] A recent replication attempt failed:
From MANCHESTERDC to LiveDC
Naming Context: CN=Configuration,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:37.
9 failures have occurred since the last success.
The guid-based DNS name
dad67b59-087c-40a2-a2fb-21bb3bd82457._msdcs.transport.local
is not registered on one or more DNS servers.
[Replications Check,LiveDC] A recent replication attempt failed:
From BRIDGENDDC to LiveDC
Naming Context: CN=Configuration,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:36.
10 failures have occurred since the last success.
The guid-based DNS name
7c485ada-9e08-4904-8f99-67184db3ed5a._msdcs.transport.local
is not registered on one or more DNS servers.
[Replications Check,LiveDC] A recent replication attempt failed:
From SOUTHAMPTONDC to LiveDC
Naming Context: CN=Configuration,DC=transport,DC=local
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failure.

The failure occurred at 2011-07-11 10:23:03.
The last success occurred at 2011-07-11 07:45:36.
10 failures have occurred since the last success.
The guid-based DNS name
11083fce-735e-425e-8a60-651d1f84a207._msdcs.transport.local
is not registered on one or more DNS servers.
……………………. LiveDC failed test Replications
Starting test: RidManager
……………………. LiveDC passed test RidManager
Starting test: Services
……………………. LiveDC passed test Services
Starting test: SystemLog
A warning event occurred. EventID: 0x000003F6
Time Generated: 07/11/2011 10:26:24
Event String:
Name resolution for the name _ldap._tcp.Head-Office._sites.dc._msdcs.southampton.transport.local timed out after none of the configured DNS servers responded.
A warning event occurred. EventID: 0x0000002F
Time Generated: 07/11/2011 10:26:54
Event String:
Time Provider NtpClient: No valid response has been received from manually configured peer time.windows.com after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable.
……………………. LiveDC failed test SystemLog
Starting test: VerifyReferences
……………………. LiveDC passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
……………………. ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
……………………. ForestDnsZones passed test
CrossRefValidation

Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
……………………. DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
……………………. DomainDnsZones passed test
CrossRefValidation

Running partition tests on : Schema
Starting test: CheckSDRefDom
……………………. Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
……………………. Schema passed test CrossRefValidation

Running partition tests on : Configuration
Starting test: CheckSDRefDom
……………………. Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
……………………. Configuration passed test CrossRefValidation

Running partition tests on : transport
Starting test: CheckSDRefDom
……………………. transport passed test CheckSDRefDom
Starting test: CrossRefValidation
……………………. transport passed test
CrossRefValidation

Running enterprise tests on : transport.local
Starting test: LocatorCheck
……………………. transport.local passed test
LocatorCheck
Starting test: Intersite
……………………. transport.local passed test Intersite

i would be greatful for any help on this as im stuck at a bit of a dead end.:neutral:

Cheers
J

[Author]

Posts