DNS Registration De-registration

  • Thread starter Thread starter Luis Jesus
  • Start date Start date
L

Luis Jesus

Hi,

I get the following error on my two DNS servers.

Event ID: 5781 Source: NETLOGON
Dynamic registration or deregistration of one or more DNS
records failed because no DNS servers are available.

Any ideas on how to fix this

LJ
 
Hi,

Thanks for all the info. I am using forwarders but am not
including them in my TCP/IP config. I just use all three
of my DNS servers. I have two DNS servers, two in one
subnet and the other server on the other subnet. I have
it setup as a Primary zone, Secondary zone for the subnet
with two servers and a Secondary for the other subnet (is
this advisable or should I use AD integrated zones??)

My domain is a single label domain (weber) I have SP4
installed on all the servers. Updates are set to yes and
the zone is weber and AD is also weber.

LJ
 
In
Paul McGuire said:
if you look in you event log this error will be time stamped. Also
look in you dns log and the dns started entry and mine the netlogon
service started .07 seconds before the DNS server. This is why you
get this message. MS has some KB articles on making netlogon
dependant on DNS to make netlogon start after DNS.

HTH

Paul McGuire
Click to expand...
I agree that it can be a startup timing issue, but if Luis installed SP4 and
he has a single label domain name, then the problem can *also* come down to
the fact that SP4 rejects single label DNS registration.

As for the startup timing, I understand from colleagues that altering the
dependency may not give the desired effects, resulting in longer boot times
and other anamolies and may be more desireable in the long run to just live
with the 5781. I've known admins to just change the zone back to a Primary
from AD Integrated, which results in the error to disappear/ Now if Luis
wants to try that and see if the error goes away, then that can be one
solution. Up to him on how he wants to handle that.

There are two options for the single label domain name:
1. Reinstall AD with the proper name. DNS can't handle non-RFC names, such
as a single label DNS name. Needs to be in the form of a 2nd level name and
a 1st level name (1st level names are also called TLDs), such as domain.com
or weber.com or weber.local, etc.

2. Reg entry to alter the DNS behavior to ignore the single label name and
force it to update for the DCs. However this is just a bandaid to force DCs
to register. Win2k clients and newer will not register into a single label
name. If that is of concern to Luis, then I would suggest option 1.
Here's the article on the bandaid (reg entry):
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names [needs the domain.com name and cannot be
just --domain--]:
http://support.microsoft.com/?id=300684

Hope that helps and explains it.



--
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
 
Back
Top