netlogon, eventID 5774

[Dirk]

LS.

We have a new clients system configuration to manage. Not to familiar with setup of w2k DNS.
NOT setup by us, just supporting it with hick-ups.
In the event viewer of the W2K server, there are lots of netlogon errors, ID 5774.
Registration of the DNS record '_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.intermodal.com. 600 IN SRV 0 100 3268 interserv.intermodal.com.' failed with the following error: DNS operation refused.
Registration of the DNS record '_ldap._tcp.dc._msdcs.intermodal.com. 600 IN SRV 0 100 389 interserv.intermodal.com.' failed with the following error: DNS operation refused.
Registration of the DNS record 'd68316d4-bb70-4ae8-9f49-00cedae93fc9._msdcs.intermodal.com. 600 IN CNAME interserv.intermodal.com.' failed with the following error: DNS operation refused.

It seems that it has influence on the internet activity of the workstations. If we do a "ipconfig /flushdns" en "ipconfig /registerdns" on the server, it will work for a while for the clients. But the errors keep coming back
What can we check (DNS settings?) and what could be the reason for this (as far as we know, there was no changes on the internal LAN).
Can we delete entries in netlogon.dns and netlogon.dnb, or delete the files without doing harm?
DNS is NOT configured with reverse lookup

Thanks,

Dirk

 

[Steve Duff [MVP]]

From your symptoms, I'm guessing you have an outside DNS server(s)
listed as a secondary on these machines.

If so, you cannot configure it this way (or you will see exactly
the sort of problems you have.)

You can only list your domain DNS server(s) in TCP/IP properties.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
LS.

We have a new clients system configuration to manage. Not to familiar with setup of w2k DNS.
NOT setup by us, just supporting it with hick-ups.
In the event viewer of the W2K server, there are lots of netlogon errors, ID 5774.
Registration of the DNS record '_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.intermodal.com. 600 IN SRV 0 100 3268 interserv.intermodal.com.' failed with the following error: DNS operation refused.
Registration of the DNS record '_ldap._tcp.dc._msdcs.intermodal.com. 600 IN SRV 0 100 389 interserv.intermodal.com.' failed with the following error: DNS operation refused.
Registration of the DNS record 'd68316d4-bb70-4ae8-9f49-00cedae93fc9._msdcs.intermodal.com. 600 IN CNAME interserv.intermodal.com.' failed with the following error: DNS operation refused.

It seems that it has influence on the internet activity of the workstations. If we do a "ipconfig /flushdns" en "ipconfig /registerdns" on the server, it will work for a while for the clients. But the errors keep coming back
What can we check (DNS settings?) and what could be the reason for this (as far as we know, there was no changes on the internal LAN).
Can we delete entries in netlogon.dns and netlogon.dnb, or delete the files without doing harm?
DNS is NOT configured with reverse lookup

Thanks,

Dirk

 

[Dirk]

Thanks,

The ISP DNS are placed in the TCP/IP properties on the w2k server. The strange thing is that the workstations are referring to the DNS of the ISP. What is the use for a internal DNS with this setup?

Regards,

Dirk
From your symptoms, I'm guessing you have an outside DNS server(s)
listed as a secondary on these machines.

If so, you cannot configure it this way (or you will see exactly
the sort of problems you have.)

You can only list your domain DNS server(s) in TCP/IP properties.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
LS.

We have a new clients system configuration to manage. Not to familiar with setup of w2k DNS.
NOT setup by us, just supporting it with hick-ups.
In the event viewer of the W2K server, there are lots of netlogon errors, ID 5774.
Registration of the DNS record '_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.intermodal.com. 600 IN SRV 0 100 3268 interserv.intermodal.com.' failed with the following error: DNS operation refused.
Registration of the DNS record '_ldap._tcp.dc._msdcs.intermodal.com. 600 IN SRV 0 100 389 interserv.intermodal.com.' failed with the following error: DNS operation refused.
Registration of the DNS record 'd68316d4-bb70-4ae8-9f49-00cedae93fc9._msdcs.intermodal.com. 600 IN CNAME interserv.intermodal.com.' failed with the following error: DNS operation refused.

It seems that it has influence on the internet activity of the workstations. If we do a "ipconfig /flushdns" en "ipconfig /registerdns" on the server, it will work for a while for the clients. But the errors keep coming back
What can we check (DNS settings?) and what could be the reason for this (as far as we know, there was no changes on the internal LAN).
Can we delete entries in netlogon.dns and netlogon.dnb, or delete the files without doing harm?
DNS is NOT configured with reverse lookup

Thanks,

Dirk

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Thanks,

The ISP DNS are placed in the TCP/IP properties on the
w2k server. The strange thing is that the workstations
are referring to the DNS of the ISP. What is the use for
a internal DNS with this setup?

You should not use your ISP's DNS in TCP/IP properties in any position on
any interface of any member of an AD domain. Long logon times and errors
will result.
Domain controllers register their service and location records in DNS, which
is the reason for your errors. Use only your local DNS server in TCP/IP
properties, even if you only have one.