Link to home
Start Free TrialLog in
Avatar of PlazaProp
PlazaProp

asked on

W2K DNS Fails, missing _msdcs, _sites, _tcp, _udp

Several times over the past couple months the _msdcs, _sites, _tcp, _udp entries on our (DNS) domain controller for our domain become missing.  We have only one DNS server.  Once this happens users cannot access network resources.  If I do a netdisag /fix all the entries are recovered/rebuilt and users can then resume normal operation.

 What would cause this to happening?

One friend mentioned checking aging/scavenging.  It was enabled to scavenge stale resource records and set to 7 days.  Allow Dynamic Update was also set to "only secure updates"

I am disabling the scavenging and changing dynamic update to yes to see if this rectifies the problem or not.  Problem is the issue seems to be random.
ASKER CERTIFIED SOLUTION
Avatar of Rich Weissler
Rich Weissler

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of PlazaProp
PlazaProp

ASKER

Chris,  I had scavenging set to 7 days check back on my reports the first time this happened was 4 weeks ago on the same day of the week.  Coincidence?

I have check updates back to secure.

Razmus. I check out the MS KB and it sound exactly like that problem we are having.  One thing that I noticed after reading the article is that dynamic DNS updates on  the NIC was turned off.

We have 2 other forward lookup zones to do some static routing.  they do not have the _msdcs and other items.  I don't think they ever have.  They are not part of the AD domain.  This wouldn't cause an issue would it?
The other two lookup zones aren't on a different server for the same domain name, right?  (I assume they aren't, but just to articulate an assumption...)

Try the scavenging for a while, but if the problem reoccurs... I'd try turning DNS dynamic updates back on.   It sounds like Microsoft has acknowledged it as a known problem with Windows 2000, and they only offer the few possible fixes.
Well,  The issue has not returned.  I had changed updates to secure and  "Scavenge Stale records" is unchecked.  The time length is set to 7 days but if the box is unchecked the time doesn't really matter.