DNS errors? What do they mean?

[Ovatvvon]

I get an error in my event viewer over and over. Just loaded on win2000 server yesturday and trying to figure this out...I'm pretty new to DNS.


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/3/2002
Time: 2:35:07 PM
User: N/A
Computer: WTWDB1
Description:
Registration of the DNS record '_ldap._tcp.dc._msdcs.jwdinfo.com. 600 IN SRV 0 100 389 wtwdb1.jwdinfo.com.' failed with the following error:
DNS server unable to interpret format.
Data:
0000: 29 23 00 00 )#..


I'm very sure I didn't setup DNS right. I don't know what I'm supposed to do to it to setup it up how it should be or to make it copy files from other DNS servers.

Does anyone know what this error means or what I can do to fix it. Or where I can go to learn how to setup DNS correctly? (I already checked out eventid.net to find out about this. Some of the stuff I understood and tried like deleteding the "." from DNS which didn't work. Other stuff I didn't understand what they were saying to do).


-Ovatvvon :-Q

 

[Ovatvvon]

I also get the following error as well:


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 8/3/2002
Time: 3:21:59 PM
User: N/A
Computer: WTWDB1
Description:
Registration of the DNS record 'e7315f9c-be0a-4d97-9e86-df030521cb6a._msdcs.jwdinfo.com. 600 IN CNAME wtwdb1.jwdinfo.com.' failed with the following error:
DNS RR set that ought not exist, does exist.
Data:
0000: 2f 23 00 00 /#..

-Ovatvvon :-Q

 

[tlcscousin]

from

http://www.eventid.net

gets this on that error.

Start of quote
Event ID: 5774
Source NETLOGON
Type Error
Description Registration of the DNS record '<dns record>'. 600 IN SRV 0 100 3268 <domain name>.' failed with the following error: <error description>.
Comments Darren Kennedy: See the link below to Registry Tweaks for a description of the problem.

Adrian Grigorof: Error: &quot;DNS server unable to interpret format.&quot; - This error message may be generated in several circumstances. See Q259277 for a general approach on troubleshooting this. In some cases this may be caused by the security setting on the parent.local server being set to only use secure updates. Changing this to allow &quot;dynamic updates&quot; (instead of only secure) might eliminate the problem.

Another newsgroup discussion thread suggested that the event was caused by the fact that the Active Directory Domain Controller running the DNS server did NOT point to itself as a DNS server (instead it used the ISP DNS servers). Changing the DNS server settings to point to itseld fixed the problem.

Joakim Bengtsson: I found that delaying startup of Netlogon service until DNS was started solved this problem. Just add DNS to the DependOnService entry in HKLM-System-CurrentControlSet-Services-Netlogon. This is described among other things in Q193888.

Sven Jedeck: This event can occur when the IP address of the server is changed.

Daniel Hamilton: This Error occurs when DNS Server has its database in Active Directory Integrated mode, and is also a Domain Controller and network adapters have been changed in the system. Fix: Delete affected zones and recreate the zones. This will allow the NETLOGON service to successfully re-register the records that were being reported in the 5774 event.

PeterI: Error: &quot;DNS RR set that ought not exist, does exist.&quot; - This can be caused by someone manually creating an alias for that namespace (in this case test.com). If none of the published fixes addresses your problem, try this instead. Open the DNS console from the MMC and expand the primary dns server. Select Forward Lookup Zones and select the target zone (test.com). There you should see an A (alias) or CNAME record. Delete it, then stop and start the netlogon service.

Johannes (Jazzy) Nielsen: Error: &quot;DNS operation refused.&quot; - The problem was the time it took logging on to the W2K server, the clients were not able to find the server and waited up to 30 min. before logging on. This was solved by configuring the internal DC as DNS servers instead of the ISP DNS.

E Soden: I had my DNS server setup as a root server, which it is not. Go to the Computer Management Console DNS snap-in and drill down to the Forward Lookup Zones. If there is a DOT zone listed &quot;.&quot; then your server is setup as a root server. Deleting the Root zone got rid of the error message.

Lou Branda: I fixed this problem by giving the Domain Computers full control the Forward Lookup Zone (the only one I had.

Adrian Grigorof: From a newsgroup post: &quot;There could be many reasons for this event. I got this error because our HQ uses a BIND DNS. Some people fixed this by deleting the problem record by hand and restart the NETLOGON service.&quot;

Adrian Grigorof: Error: &quot;A socket operation was attempted to an unreachable host.&quot; - Apparently, the DNS server is not reachable. This could be due to network problems (cables, hubs, etc...) or the server may be down (or the IP address changed). Verify that there is connectivity between the computer reporting the problem and the DNS servers where is trying to register.

Slister: Error: &quot;DNS server unable to interpret formula&quot;. I got this error using Cisco Network Registrar version 5 for my DNS server which is authoritative for the primary zone where my Active Directory structure lives. On the domain controller that controls the domain of the same name as the primary zone in DNS, I get the event ID 5774 every two hours. Cisco sent me a hack that will make CNR fool a domain contoller into believing it has successfully updated the record when in reality, it hasn't and it cannot. Here's the hack:

nrcmd>session set visibility=3
nrcmd>dns enable simulate-zone-top-dynupdate

I've tested this in my lab and it works (but only on CNR as of version 5.0.1 - earlier versions don't recognize the command).

Jh: I received this event because the DNS service on my Windows 2000 server was bound to a second IP address configured on that server.
Our Approach This information is only available to subscribers. An example of &quot;approach&quot; is available here.
Links Q259277 , Q284963 ,

http://www.microsoft.com/TechNet/win2000/win2ksrv/reskit/tcpch06.asp,

Q193888 , Registry Tweaks, Q265706 , Diagnosing and Troubleshooting Active Directory Problems

 

[hackmaster]

I had the same problem myself, but was able to fix it

Microsoft Knowledge Base Article - Q260371 -
Troubleshooting Common Active Directory Setup Issues in Windows 2000

Read over and follow this article very carefully, it all has to do with setting up DNS for Active Directory just the right way for it to dynamically register properly. I spent months trying to fix this same error with no success until I found this article just recently! Let me know if it helps!