Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 2088 Source: NTDSReplication

Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups group policy users and computers and their passwords Active Directory successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.

Invalid DNS configuration may be affecting other essential operations on member computers domain controllers or application servers in this Active Directory forest including logon authentication or access to network resources.

You should immediately resolve this DNS configuration error so that this domain controller can resolve the IP address of the source domain controller using DNS.

Alternate server name: <name>
Failing DNS host name: <name>

NOTE: By default only up to 10 DNS failures are shown for any given 12 hour period even if more than 10 failures occur. To log all individual failure events set the following diagnostics registry value to 1:

Registry Path: HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client

User Action:

1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID remove the source domain controller's metadata with ntdsutil.exe using the steps outlined in MSKB article 216498.

2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".

3) Verify that the source domain controller is using a valid DNS server for DNS services and that the source domain controller's host record and CNAME record are correctly registered using the DNS Enhanced version of DCDIAG.EXE available on

dcdiag /test:dns

4) Verify that that this destination domain controller is using a valid DNS server for DNS services by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller as follows:

  dcdiag /test:dns

5) For further analysis of DNS error failures see KB 824449:

Additional Data
Error value: 11004 The requested name is valid but no data of the requested type was found.
For me, this error went away, when we added IPs of DNS servers (DCs) of root domain as Forwarders in DNS properties of local DCs.
Failure to resolve the source domain controller name by using the CNAME resource record in DNS can be due to DNS misconfigurations or delays in DNS data propagation. See the links to T737678 (Fixing Replication DNS Lookup Problems), T787713 (DNS lookup failure occurred with replication success), and TB727057 (Troubleshooting Active Directory Replication Problems) for more information on this event.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.