Active Directory Lightweight Directory Services could not use DNS to resolve the IP address of the source domain controller ...

Active Directory Lightweight Directory Services 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 Lightweight Directory Services 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 Lightweight Directory Services 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: 
 %1 
Failing DNS host name: 
 %2 
 
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\%5\%6 
 
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 Lightweight Directory Services and is accessible on the network by typing "net view \\" or "ping ". 
 
 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 http://www.microsoft.com/dns 
 
  dcdiag /test:dns 
 
 4) Verify 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: 
   http://support.microsoft.com/?kbid=824449 
 
Additional Data 
Error value: 
 %3 %4