Question Locked

Windows 2003 server DNS Problem

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi Everyone:
I am getting the following error in System Event Viewer and i'm trying to resolve whatever the issue may be that is causing this error. I have checked eventid.net and tried a couple of different things that I read there, but nothing has made this go away.

Has anyone else had this error and if so, what did you do to resolve it?

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 3/20/2007
Time: 10:05:36 AM
User: N/A
Computer: ZION
Description:
The dynamic registration of the DNS record '25c781d8-192d-4bf5-b4f2-1a1201b22495._msdcs.domain.local. 600 IN CNAME server.domain.local.' failed on the following DNS server:

DNS server IP address: 192.168.0.2
Returned Response Code (RCODE): 5
Returned Status Code: 9016

For computers and users to locate this domain controller, this record must be registered in DNS.

USER ACTION
Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. You can find this program on the Windows Server 2003 installation CD in Support\Tools\support.cab. To learn more about DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain controller or restart Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.
Or, you can manually add this record to DNS, but it is not recommended.

ADDITIONAL DATA
Error Value: DNS signature failed to verify.

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

5 replies

by cg it

EventID.net is a great source for investigating event codes found in the logs, but in this case, the event tells you what the probable cause is, what tests to run to resolved the problem or what to do to resolve the problem.

by balfour

here are the results:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>dcdiag.exe

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

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

Doing primary tests

Testing server: Default-First-Site\ZION
Starting test: Replications
......................... ZION passed test Replications
Starting test: NCSecDesc
......................... ZION passed test NCSecDesc
Starting test: NetLogons
......................... ZION passed test NetLogons
Starting test: Advertising
......................... ZION passed test Advertising
Starting test: KnowsOfRoleHolders
......................... ZION passed test KnowsOfRoleHolders
Starting test: RidManager
......................... ZION passed test RidManager
Starting test: MachineAccount
......................... ZION passed test MachineAccount
Starting test: Services
......................... ZION passed test Services
Starting test: ObjectsReplicated
......................... ZION passed test ObjectsReplicated
Starting test: frssysvol
......................... ZION passed test frssysvol
Starting test: frsevent
......................... ZION passed test frsevent
Starting test: kccevent
......................... ZION passed test kccevent
Starting test: systemlog
......................... ZION passed test systemlog
Starting test: VerifyReferences
......................... ZION passed test VerifyReferences

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

Starting test: CheckSDRefDom
......................... TAPI3Directory passed test CheckSDRefDom

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

Running enterprise tests on : PMI.local
Starting test: Intersite
......................... PMI.local passed test Intersite
Starting test: FsmoCheck
......................... PMI.local passed test FsmoCheck

C:\Documents and Settings\Administrator>

by debc-cpsource

I was wondering how you resolved this issue? We are having the exact same problem with a client and have been unable to correct it.

Any help would be much appreciated!

TIA
Deb Collins
CPSource LLC
Somers Point, NJ

by balfour

I haven't gotten this issue resolved, although I cannot really pinpoint any negative effects on our domain. I have tried a bunch of different things, but none of them have worked.

Please keep me updated as to how you proceed and if you get it resolved, how you did it.

This discussion is closed to new replies.