Reoccurring event log message

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an advanced 2000 server and keep receiving the following error
messages every couple of minutes. I am not that familiar with DNS, so any
assistance or direction to resources will greatly be appreciated. Please see
the following two messages from the event log.

Thanks,

Ron


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 9/10/2005
Time: 10:40:18 AM
User: N/A
Computer: SERVER
Description:
Registration of the DNS record
'_ldap._tcp.pdc._msdcs.server.walkerrobinson.com. 600 IN SRV 0 100 389
server.server.walkerrobinson.com.' failed with the following error:
DNS server unable to interpret format.
Data:
0000: 00002329

Next:

Event ID: 5774
Date: 9/10/2005
Time: 10:09:57 AM
User: N/A
Computer: SERVER
Description:
Registration of the DNS record '_kpasswd._udp.server.walkerrobinson.com. 600
IN SRV 0 100 464 server.server.walkerrobinson.com.' failed with the following
error:
DNS server unable to interpret format.
Data:
0000: 00002329
 
Ron B said:
I have an advanced 2000 server and keep receiving the following error
messages every couple of minutes. I am not that familiar with DNS, so
any assistance or direction to resources will greatly be appreciated.
Click to expand...

Most likely these events are caused from you having your ISP's DNS in TCP/IP
properties.

Most likely when you promoted your server to a DC, it configured itself as a
DNS server. So, in TCP/IP properties, this DC and all member clients must
use this DCs address for DNS only

Change the DNS server in TCP/IP properties to its own address only, run
ipconfig /flushdns ipconfig /registerdns then restart the Netlogon Service.
 
I have the same problem.

In my case, the server is the PDC and the DNS for the AD is on this server.
This DNS is a root DNS. If the IP for this machine is placed at the top of
the NIC's DNS entrys, the 5774 error problem dissapears. However, this
machine will not be able to resolve external domain names either with a Ping
command or from the browser for example.

It appears that even though the ISP's lookup DNS is listed second and third
on the NIC's list of DNS servers, those DNS will not be used to lookup domain
names that are not returned by the local DNS.

The Local DNS server properties has a forwarders tab which should forward
all unresolved requrest to another DNS IP but this function is disabled
apparently because this is a root DNS server.
 
RobGMiller said:
I have the same problem.

In my case, the server is the PDC and the DNS for the AD is on this
server. This DNS is a root DNS. If the IP for this machine is placed
at the top of the NIC's DNS entrys, the 5774 error problem
dissapears. However, this machine will not be able to resolve
external domain names either with a Ping command or from the browser
for example.

It appears that even though the ISP's lookup DNS is listed second and
third on the NIC's list of DNS servers, those DNS will not be used to
lookup domain names that are not returned by the local DNS.

The Local DNS server properties has a forwarders tab which should
forward all unresolved requrest to another DNS IP but this function
is disabled apparently because this is a root DNS server.
Click to expand...

Delete the forward lookup zone named with a dot ".". Then you can enable a
forwarder, you must remove the ISP DNS from TCP/IP properties.
 
Back
Top