Deregistration of dns record ....

[Juan]

This error mensage appears in the event log every an hour , hour and a half
and I cant understand what`s going wrong because everything else seems to be
working OK except for this error.
What could be happening

Thanks in advance

Juan

PD :
I attach a copy of the error message

-----------------------------------------------------
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 19/08/2003
Time: 02:42:58 p.m.
User: N/A
Computer: WEBTOP
Description:
Deregistration of the DNS record
'_kerberos._tcp.Default-First-Site-Name._sites.topsystems.com.uy. 600 IN SRV
0 100 88 webtop.topsystems.com.uy.' failed with the following error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..
---------------------------------------------------------

 

[Ace Fekay [MVP]]

In

This error mensage appears in the event log every an hour , hour and
a half and I cant understand what`s going wrong because everything
else seems to be working OK except for this error.
What could be happening

Thanks in advance

Juan

PD :
I attach a copy of the error message

-----------------------------------------------------
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 19/08/2003
Time: 02:42:58 p.m.
User: N/A
Computer: WEBTOP
Description:
Deregistration of the DNS record
'_kerberos._tcp.Default-First-Site-Name._sites.topsystems.com.uy. 600
IN SRV 0 100 88 webtop.topsystems.com.uy.' failed with the following
error:
DNS operation refused.
Data:
0000: 2d 23 00 00 -#..
---------------------------------------------------------

Hi Juan

This is indicative of using an ISP's DNS server in your IP properties.
Numerous errors result from this, too many to mention, yours being one of
them. All machines in an AD environment (DCs and clients) should ONLY use
your internal DNS server, that's it. Reason is AD stores all it's
information in DNS. Whenver it "looks" for something, it queries DNS. In
your situation, the netlogon service is trying to register/de-register info
into DNS and apparently it's aksing this of a DNS server that either
doesn;'t host the AD zone info, such as your ISP's or that updates are not
set to at least "YES"

To get efficient Internet resolution, I would suggest to setup a Forwarder.
If the option is grayed out, delete the Root zone. Both procedures are
outlined in this article under Step3:
http://support.microsoft.com/?id=3200202

Hope that helps.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory