Error 5774 with DNS? 3

[krakatow2]

I have 3 DNS servers set up in an Win2000 domain. Since a bit of playing around with the DNS setup (created a site and deleted it etc) the servers are coming up with Error 5774 every 15 minutes or so. The error message is always something like

"Registration of the DNS record 'blah blah blah' failed with the following error:
No records found for given DNS query. "
Other messages are similar but state that Deregistration of the DNS record failed.


I've tried everyting I can to get rid of them but they still keep coming up, even after deleting the zone in DNS.
Any help would be great.
Regards

 

[axslinger]

I have had similar errors in Win2K server. Still haven't found an answer. Some of the messages I get are "unrecognizable format" or something along those lines. If you get an answer to this, please pass it along.

Brian

 

[bitsnpcs]

Is the IP address of your DNS server the Primary DNS entry in the TCP/IP settings.

I was getting similar errors on my Domain controller, which is also the DNS server. When I put its IP address as the Primary DNS, they went away.

But now I'm getting the following error I have not been able to troubleshoot:

Date: 2/2/01 Source: NETLOGON
Time: 11:43 Catagory: None
Type: Error Event ID: 5774
User: N/A
Computer: server1

Description:
Registration of the DNS record "domain.com" 600 IN A 193.169.0.4" failed with the following error:
A connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connection host has failed to respond.

I also get the same error for "_ldap_tcp.domain.com 600 IN SRV 0 100 389 server1.domain.com"

It is a W2K Domain controller and DNS is running on this machine.

TIA

 

[jahlmer]

These messages are Active Directory trying to register SRV records dynamically with the DNS Server specified.

Go into the DNS manager and then right click the zone (folder with the domain name on it) make certain dynamic updates are enabled.

If that checks out okay try rightclicking the Server name/properties in the Advanced properties tab. go to name checking and change it to the "any character option" if this resolves it he has an oddball hostname or domain name. (space, special character etc.) Note: I think you can use a - in a hostname, but generally speaking, DNS assumes there wont be any - in a domain name. on the server

 

[garrett]

I've had similar dynamic registration problems on a reboot, when the a domain controller was also a DNS server that was AD integrated. Basically, if the domain controller was pointing to itself (in the LAN connection settings) as its primary DNS server, when it was rebooted an attempt to dynamically register with DNS was made, but the DNS server service was not completely started. So the registration failed. Since we had several DNS servers we just made sure each one pointed to the other instead of to itself. I believe there was a technet article on this problem.

 

[DeanT]

The above article sounds like the most likely explanation.
Let me summarize everyone's input.
1)Make sure that your Zone's (forward and reverse) are configured to "allow dynamic updates"
2)Make sure that the Primary IP address for the DNS server is configured correctly (the DC's IP)
3)If in fact it is a matter of the DC trying to register before the DNS server is fully funcional, then try going to a command prompt and use the ipconfig utility.
ipconfig /registerdns
which will force the server to try registering the DNS values again. If that doesn't work I would remove DNS, delete the DNS directory and re-install DNS.
hope that this helps...

 

[Guest_imported]

Learn to use Google.com

http://support.microsoft.com/support/kb/articles/Q259/2/77.ASP

 

[Marcd]

bitsnpcs, did you find a way around the 5774 errors. I am getting the exact same problem and exact same errors.

I have tried the info on the Microsoft site, and on eventid. I have also tried the various suggestions made in this post.

Does anybody else have the same error?

Thanks in advance

 

[bsingin64]

Of course other people have the same error...including me....and what really boggles me...is that this error has been ocurring since the begginning of our system..even after 2 Format and restores on BOTH servers. The Dns points to the other replicating dns server...both of which are WIn2k AD integrated DCs / Dns servers. There is No DHCP and about 15 total computers on the network. we run through a Dlink Dss-24+ switch. its always the same error of 5774, unable to interperit format. were Boggled here...

 

[Marcd]

We managed to get rid of the errors by deleting the DNS zone and recreating a new one using the same name as the server (server.mydomain.com). The previous zone used a different name (dns.mydomain.com).

Regards

 

[bsingin64]

That would be a quick fix, if you didnt need replication. A Forward zone should look to the domain name. (mydomain.com). If it is pointing to a specific server, it will have problems replicating with the other server, because the other server will want to use the domain's system share (active directory shares), and it will be confused because the zone name is pointed to only the one server. the errors you might get in this situation will be file replication errors, or dns replication errors on the server OTHER than the server whose name is the zone name.

(anyhow) We tried that, and the domain fell apart.

What I think might work is to ask Microsoft, using one of our 5 support tickets....I will think about it