Unexplained Event ID 5774

[Chris]

Hello,

I'm receiving a lot of 5774 errors. KB article 284963
says to add the IP address of the server to the top of the
DNS Server Box. I did that and restarted netlogon.
Afterwards all the boxes EXCEPT for the server could
access the internet (I have a IP address from a corporate
backbone configured for Fast 0/0 in a router and there is
a switch, connecting the boxes, that goes into Fast 0/1,
everything is static IPs). If I go back to the DNS Server
Box, and use the arrows to move the DNS address above the
server's IP address and restart netlogon, then not only do
the clients still have internet access but the server can
access the internet as well. I didn't delete the IP of
the server, just moved it from the top to below the DNS
address. I'm still getting the 5774 events.

Thanks,

--Chris

 

[Steve Duff [MVP]]

It isn't clear what you are referring to
by "DNS address".

You must name, and can only name,
"inside" DNS servers that host AD information
for the domain.

So if you mean an outside DNS server, you
can't name it at all. If you mean a different
AD DNS server on your domain,
it shouldn't really matter which order
you put them in.

If you list the server's own IP, then (1) it must
be running the DNS service, (2) must be
authoritative for the domain and accept dynamic
updates, (3) its DNS server must have root hints and/or
forwarders enabled and must not have a root (".") zone
if you want to access public DNS names on the internet.

Steve Duff, MCSE
Ergodic Systems, Inc.

 

[TIM ROBERTS]

Hi Chris,
Usally the 5774 Event ID is a configuration error. So make sure your (the
Nic settings) are pointing to a valid DNS on the internal Lan. If you have
two DNS server (Example DNS1 and DNS 2) and DNS1 is this server we are
talking about. Have DNS1 point to DNS2 for Perfered DNS and Then list dns1
as alternate. On DNS2 have it point to DNS 1 for perfered and itseld\f for
aler nate. This would not apply if you had more than two DNS server. If you
had three or more DNS servers (DNS1, DNS2 and DNS3) Point DNS1to DNS2 for
perfered and itself for alternate. Have DNS2 point to DNS1 and then itself
as alternate and have DNS3 point to DNS1 and itself for alternate.
The zone should be AD and they should be set to allow DDS updates. Configure
forwaders to point to either a up stream DNS server (ISP) or in your case
maybe the campus has a bind server or Public DNS server. Also 5774 error can
be caused by bad delagation of zones as well. If its a AD zone, try going
into C:\winnt\system32\config look for netlogon.dns and netlogon.dnb, rename
them to .123 and .456. Then do net stop netlogon and net start netlogon.
Clear your all logs in the event viewer.
If you cannot figure this out i can provide you with a way to have netmon
run and when the error is trigged it will stop. Then you have a trace as
well. You can also enabled logging on the server, Chaeck all of them you
could also use the dnscmd comands to out your information.
Let me know if this helps.

Tim

 

[Ace Fekay [MVP]]

In

I don't believe that I have named "outside" DNS servers
and there's no ISP at all that would provide an address as
well. I do have a root DNS zone and since this is an
internal LAN, it shouldn't matter that it exists, right?

What Steve means as "outside" is not to use any DNS server that does NOT
hosting a copy of the AD zone name. If you have any other server that does
not host the zone name for AD, numerous errors will occur, including 5774.
If you need some other server in your network to be available for lookups,
setup a Forwarder to that server from your DNS server so the clients will
query AD's DNS server and if it doesn't have the answer, it will "forward"
the request to the other server, etc.




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

 

[Ace Fekay [MVP]]

In

Thanks for the replies gentlemen... unfortunately, still
having major problems here!!!!

Here's the details of my 5774 errors:

Registration of the DNS record
'_ldap._tcp.Default-First-Site._sites.OASFO.local. 600
IN SRV 0 100 389 Homer.OASFO.local.' failed with the
following error:
DNS name does not exist.

Registration of the DNS record
'_ldap._tcp.Default-First-
Site._sites.gc._msdcs.OASFO.local.
600 IN SRV 0 100 3268 Homer.OASFO.local.' failed with
the following error:
DNS name does not exist.

Registration of the DNS record
'_kerberos._tcp.Default-First-
Site._sites.dc._msdcs.OASFO.local.
600 IN SRV 0 100 88 Homer.OASFO.local.' failed with
the following error:
DNS name does not exist.

I'm getting lost because in my forward lookup zone, the
_msdcs, _sites, _tcp, and _udp folders do exist. So, I
ran netdiag /fix and it failed miserably at finding those
paths and at the very end I received a line that said
something about the DNS address not being configured.

I went to both the DNS tab from TCP/IP props and both
addresses (as mentioned in a previous post) are in there.
I went to the properties of the forward lookup zone and
again both addresses are listed.

Any assistance is greatly appreciated!

Thanks,

--Chris

This is usually a DNS misconfiguration and/or Primary DNS Suffix being
missing/incorrect or the name is spelled wrong in one of the configurations.

Chris, instead of guessing to what the problem is, can you post this info to
better assist you with? It would help us narrow down the issue

1. Unedited ipconfig /all
2. The AD DNS domain name
3. The spelling of the zone in DNS
4. If the zone has updates set to at least YES.

Thank you.

If reluctant to post it in public, you can email me directly.


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

 

[Chris]

Ace,

Sent you an e-mail to your Hotmail account, with the
information requested below (around 9:40 am EDT, 8/27).
Didn't feel 100% sure about giving some of that info to
the whole world. At any rate, while composing the mail to
you I noticed the errors below have the domain
as "OASFO.local" and the ipconfig gives
back "oasfo.local". Not sure if this is the problem that
you and others have eluded too... and I'd like to know how
all CAPS got in the domain name; I like to use all small
case in computer names, domains, etc., (and is there a way
to fix it).

Thanks,

--Chris

 

[Ace Fekay [MVP]]

In

Ace,

Sent you an e-mail to your Hotmail account, with the
information requested below (around 9:40 am EDT, 8/27).
Didn't feel 100% sure about giving some of that info to
the whole world. At any rate, while composing the mail to
you I noticed the errors below have the domain
as "OASFO.local" and the ipconfig gives
back "oasfo.local". Not sure if this is the problem that
you and others have eluded too... and I'd like to know how
all CAPS got in the domain name; I like to use all small
case in computer names, domains, etc., (and is there a way
to fix it).

Thanks,

--Chris

Well, when you configured your AD domain name, you must have used caps. In
your Primary DNS Suffix, you must have used lower case, hence what ipconfig
/all gives back in it's results.

I sent you a reply. Did you get 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