Active Directory could not resolve DNS host name

We are running windows 2003 EE. we are using two domain controller one is DC
& other is ADC. both DC are also working as AD integrated DNS server. but
when ever i restart my DC a always get this error:

Event Type: Error
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 2087
Date: 8/29/2006
Time: 8:23:17 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: MESH
Description:
Active Directory could not resolve the following DNS host name of the source
domain controller to an IP address. This error prevents additions, deletions
and changes in Active Directory from replicating between one or more domain
controllers in the forest. Security groups, group policy, users and computers
and their passwords will be inconsistent between domain controllers until
this error is resolved, potentially affecting logon authentication and access
to network resources.

Source domain controller:
Server2
Failing DNS host name:
6e0d047e-eeff-4db8-a919-5c9e4ca8dd69._msdcs.bideonline.com

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 http://www.microsoft.com/dns

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:
http://support.microsoft.com/?kbid=824449

Additional Data
Error value:
11004 The requested name is valid, but no data of the requested type was
found.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

just after this error we recived this warning

Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1308
Date: 8/29/2006
Time: 8:26:44 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: MESH
Description:
The Knowledge Consistency Checker (KCC) has detected that successive
attempts to replicate with the following domain controller has consistently
failed.

Attempts:
1
Domain controller:
CN=NTDS
Settings,CN=Server2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bideonline,DC=com
Period of time (minutes):
687

The Connection object for this domain controller will be ignored, and a new
temporary connection will be established to ensure that replication
continues. Once replication with this domain controller resumes, the
temporary connection will be removed.

Additional Data
Error value:
1908 Could not find the domain controller for this domain.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


importnat thing is that this error & warning occurs only in Dc not in ADC.
ADC just provide one warning about file Replication service which is event ID
13508.

When I run Dcdiag on DC i found this result

Dcdiag Result
__________________________________________________________________
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MESH
Starting test: Connectivity
......................... MESH passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MESH
Starting test: Replications
......................... MESH passed test Replications
Starting test: NCSecDesc
......................... MESH passed test NCSecDesc
Starting test: NetLogons
......................... MESH passed test NetLogons
Starting test: Advertising
......................... MESH passed test Advertising
Starting test: KnowsOfRoleHolders
......................... MESH passed test KnowsOfRoleHolders
Starting test: RidManager
......................... MESH passed test RidManager
Starting test: MachineAccount
......................... MESH passed test MachineAccount
Starting test: Services
......................... MESH passed test Services
Starting test: ObjectsReplicated
......................... MESH passed test ObjectsReplicated
Starting test: frssysvol
......................... MESH passed test frssysvol
Starting test: frsevent
......................... MESH passed test frsevent
Starting test: kccevent
......................... MESH passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC00038BB
Time Generated: 08/29/2006 08:22:30
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000423
Time Generated: 08/29/2006 08:23:51
Event String: The DHCP service failed to see a directory server
An Error Event occured. EventID: 0x00000423
Time Generated: 08/29/2006 08:24:19
Event String: The DHCP service failed to see a directory server
......................... MESH failed test systemlog
Starting test: VerifyReferences
......................... MESH passed test VerifyReferences

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

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

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

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

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

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

Running partition tests on : bideonline
Starting test: CrossRefValidation
......................... bideonline passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... bideonline passed test CheckSDRefDom

Running enterprise tests on : bideonline.com
Starting test: Intersite
......................... bideonline.com passed test Intersite
Starting test: FsmoCheck
......................... bideonline.com passed test FsmoCheck

IP config Result
__________________________________________________________________
Windows IP Configuration

Host Name . . . . . . . . . . . . : mesh
Primary Dns Suffix . . . . . . . : bideonlne.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bideonlne.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet
NIC
Physical Address. . . . . . . . . : 00-05-1C-01-69-8A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.0.4

Please help me to solve this problem
.

Relevant Pages

  • Re: AD management snap in cannot find DC
    ... I ran ipconfig /flushdns on both DC and workstation ... If you are trying to connect to a domain controller running Windows ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.active_directory)
  • Re: Unwell Server :(
    ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... SBS2003 do u have configured one or more domain controller for the backup ... We have a customer with SBS2003 and every week or so the server fails to ...
    (microsoft.public.windows.server.general)
  • Re: RSOP Access denied at 1 of 5 DCs
    ... Domain Controller Authentication certificate. ... PASS - All the DNS entries for DC are registered on DNS server ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.group_policy)
  • Re: Cannot join domain...very odd
    ... Domain Controller Diagnosis ... Running partition tests on: TAPI3Directory ... Starting test: CrossRefValidation ... The DNS servers used by this computer for name resolution are not ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC
    ... On the client and server flush dns configuration, you can rightclick in the NIC card and choose repair or you can do it from cmd "ipconfig /flushdns". ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... to domain controller as below, and manually select the DC it connects to the domain and DC. ...
    (microsoft.public.windows.server.active_directory)
Loading