Unable to open DNS service console and perform AD replication to one DC ?

People,

Can anyone here please share the steps to fix this issue where the Repadmin result is showing error fromPRODDC01-VM 192.168.1.200 into PRODDC02-VM192.168.1.201 ?

and also I cannot manage the PRODDC02-VM DNS from locally or fromPRODDC01-VM.

Here is some additional information:

PRODDC01-VM DCDIAG:

PS C:\> dcdiag

Directory Server Diagnosis

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

Doing initial required tests

   Testing server: SYDNEY\PRODDC01-VM
      Starting test: Connectivity
         ......................... PRODDC01-VM passed test Connectivity

Doing primary tests

   Testing server: SYDNEY\PRODDC01-VM
      Starting test: Advertising
         ......................... PRODDC01-VM passed test Advertising
      Starting test: FrsEvent
         ......................... PRODDC01-VM passed test FrsEvent
      Starting test: DFSREvent
         There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL replication problems may cause Group Policy problems.
         ......................... PRODDC01-VM failed test DFSREvent
      Starting test: SysVolCheck
         ......................... PRODDC01-VM passed test SysVolCheck
      Starting test: KccEvent
         ......................... PRODDC01-VM passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... PRODDC01-VM passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... PRODDC01-VM passed test MachineAccount
      Starting test: NCSecDesc
         ......................... PRODDC01-VM passed test NCSecDesc
      Starting test: NetLogons
         ......................... PRODDC01-VM passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... PRODDC01-VM passed test ObjectsReplicated
      Starting test: Replications
         REPLICATION LATENCY WARNING
         ERROR: Expected notification link is missing.
         Source PRODDC02-VM
         Replication of new changes along this path will be delayed.
         This problem should self-correct on the next periodic sync.
         ......................... PRODDC01-VM passed test Replications
      Starting test: RidManager
         ......................... PRODDC01-VM passed test RidManager
      Starting test: Services
         ......................... PRODDC01-VM passed test Services
      Starting test: SystemLog
         A warning event occurred.  EventID: 0x0000000C
            Time Generated: 11/17/2016   20:44:40
            Event String:
            Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source
, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain
hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domai
n, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function a
s the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this c
omputer, you may choose to disable the NtpClient.
         A warning event occurred.  EventID: 0x000727AA
            Time Generated: 11/17/2016   20:44:45
            Event String:
            The WinRM service failed to create the following SPNs: WSMAN/PRODDC01-VM.KTM.COM; WSMAN/PRODDC01-VM.
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 11/17/2016   20:44:57
            Event String:
            Name resolution for the name KTM.COM timed out after none of the configured DNS servers responded.
         A warning event occurred.  EventID: 0x0000168D
            Time Generated: 11/17/2016   20:45:31
            Event String:
            The following DNS server that is authoritative for the DNS domain controller locator records of this domain controller does not support dynamic DNS updates:
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 11/17/2016   20:45:31
            Event String:
            Name resolution for the name KTM.COM timed out after none of the configured DNS servers responded.
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 11/17/2016   20:46:02
            Event String:
            Name resolution for the name KTM.COM timed out after none of the configured DNS servers responded.
         A warning event occurred.  EventID: 0x00001796
            Time Generated: 11/17/2016   20:54:40
            Event String:
            Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
         ......................... PRODDC01-VM passed test SystemLog
      Starting test: VerifyReferences
         ......................... PRODDC01-VM 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 : KTM
      Starting test: CheckSDRefDom
         ......................... KTM passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... KTM passed test CrossRefValidation

   Running enterprise tests on : KTM.COM
      Starting test: LocatorCheck
         ......................... KTM.COM passed test LocatorCheck
      Starting test: Intersite
         ......................... KTM.COM passed test Intersite
PS C:\>

PRODDC02-VM DCDIAG:

PS C:\Users\Administrator.KTM> dcdiag

Directory Server Diagnosis

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

Doing initial required tests

   Testing server: SYDNEY\PRODDC02-VM
      Starting test: Connectivity
         The host 94ddd95e-a625-4e14-987d-fca5ab9fdf59._msdcs.KTM.COM could not be resolved to an IP address. Check the
         DNS server, DHCP, server name, etc.
         Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
         ......................... PRODDC02-VM failed test Connectivity

Doing primary tests

   Testing server: SYDNEY\PRODDC02-VM
      Skipping all tests, because server PRODDC02-VM is not responding to directory service requests.


   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 : KTM
      Starting test: CheckSDRefDom
         ......................... KTM passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... KTM passed test CrossRefValidation

   Running enterprise tests on : KTM.COM
      Starting test: LocatorCheck
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
         A Good Time Server could not be located.
         ......................... KTM.COM failed test LocatorCheck
      Starting test: Intersite
         ......................... KTM.COM passed test Intersite
PS C:\Users\Administrator.KTM>

From the below screenshot, you can see that the AD object created from PRODDC02-VM 192.168.1.201 is replicated successfully in PRODDC01-VM 192.168.1.200

Any help would be greatly appreciated.

Thanks.

/* Server Support Specialist */