DNS stops caching pages?

[Chris Richards]

I have a Windows 2000 machine that is acting as DC, DHCP
server, DNS Server, and file server. The DNS server is
authoritative for our domain and also handles recursive
queries for the Internet. Periodically, this machine will
just decide to not handle recursive queries any more.
What this means is that once an entry times out of the
cache, a new query for name resolution will not work.
However, queries to the the DNS for hostids in the domain
for which it is authoritative DO work. In order to
resolve this, all I have to do is stop and restart DNS,
and everything will work fine for two or three days.

I had thought there was a cache pollution issue of some
kind, so I found the relevant KB article and performed the
registry mod, but that doesn't seem to have solved the
problem. I'm not getting any errors in my event log
except for two: one from my time server indicating that
it can't find its time source (because I sync to the Naval
Observatory, and it can't resolve the name). The other
one I'm a little mystified about, because it is coming
from NetLogon about every 3 hours:

Event ID: 5781
Dynamic Registration or Deregistration of one or more DNS
records failed because no DNS servers are available.

I looked this up, and none of the explanations make any
sense with regard to what is actually occurring on my
network.

HELP!!!!

Later,
Chris

 

[Kevin D. Goodknecht]

I have a Windows 2000 machine that is acting as DC, DHCP
server, DNS Server, and file server. The DNS server is
authoritative for our domain and also handles recursive
queries for the Internet. Periodically, this machine will
just decide to not handle recursive queries any more.
What this means is that once an entry times out of the
cache, a new query for name resolution will not work.
However, queries to the the DNS for hostids in the domain
for which it is authoritative DO work. In order to
resolve this, all I have to do is stop and restart DNS,
and everything will work fine for two or three days.

I had thought there was a cache pollution issue of some
kind, so I found the relevant KB article and performed the
registry mod, but that doesn't seem to have solved the
problem. I'm not getting any errors in my event log
except for two: one from my time server indicating that
it can't find its time source (because I sync to the Naval
Observatory, and it can't resolve the name). The other
one I'm a little mystified about, because it is coming
from NetLogon about every 3 hours:

Event ID: 5781
Dynamic Registration or Deregistration of one or more DNS
records failed because no DNS servers are available.

I looked this up, and none of the explanations make any
sense with regard to what is actually occurring on my
network.

Can you post an ipconfig /all?

 

[Chris Richards]

Note that the actual IP addresses and names have been
changed to protect the foolish. However, this is
representative of the actual output.


Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : fredserver
Primary DNS Suffix . . . . . . . : freds-domain
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : freds-domain

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3123
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8B-BE-35-
17

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 172.15.21.21

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 172.15.21.44

DNS Servers . . . . . . . . . . . : 172.15.21.21
Primary WINS Server . . . . . . . : 172.15.21.21

 

[Kevin D. Goodknecht]

Note that the actual IP addresses and names have been
changed to protect the foolish. However, this is
representative of the actual output.


Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : fredserver
Primary DNS Suffix . . . . . . . : freds-domain
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : freds-domain

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3123
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8B-BE-35-
17

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 172.15.21.21

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 172.15.21.44

DNS Servers . . . . . . . . . . . : 172.15.21.21
Primary WINS Server . . . . . . . : 172.15.21.21

Thanks for the ipconfig The cause of the 5781 is your domain is a single
label name(domain vs. domain.com, no dot in the name) this causes
registration problems for Win2kSP4, Win XP Pro, and Win2k3. Apply the
registry entry from this KB article:
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&FR=1

 

[Chris Richards]

Thanks for that link. Think that will solve my other
problem as well?

 

[Kevin D. Goodknecht]

In

Thanks for that link. Think that will solve my other
problem as well?

It won't hurt, your internal DNS is probably overloaded trying to resolve
the illegal name.
Let's clear up the 5781s and go from there. Make sure DNS is set up as per
this KB: 300202 - HOW TO Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&FR=1

 

[Chris Richards]

Finally got the registry entries modified per KB 300684
this weekend. It looks to have resolved my 5781s. My DNS
hasn't broken either, although it may still be too early
to be positive on that, given the sporadic nature of the
failure.

Later,
Chris

 

[Kevin D. Goodknecht]

In

Kevin,
Thanks very much for your assistance. All issues appear
to have resolved themselves since applying the registry
change from KB 300684. Everything is running smoothly and
I've not had any further NetLogon or DNS problems since.

Well, that's a good deal, sure glad it helped you.