Windows 2003 DNS Aging and Scavenging Questions ?
I have a client that has a 900 user enviorments with 3 Windows 2003 R2 domain controllers running DNS servers. The scavaging was not enabled for over 5 years and most IPs in DNS have 2-3 different names assigned to it. I followed several technet articles on setting up DNS Aging and Scavenging , all of them have the same instructions and advice. So far 10 days have passed and I have seen any progress, I still have 2100 records for 900 machines. Can anyone share some info on what it typically an issue here.
http://blogs.technet.com/n
Not sure if you saw that blog entry but it is one of the best around for scavenging.
Not sure if you saw that blog entry but it is one of the best around for scavenging.
ASKER
Thats the same blog I used. The next scavage time the 28th set set to scavage every 7 days. All records are checked to scavage when stale, some time stamps are back in 2004
You should find event log entries indicating that the Scavenging process ran. I would be interested in the data within that, especially whether or not it considers anything suitable for Scavenging.
Otherwise, if the Refresh Interval is long the zone won't be Scavenged until at least one full Refresh interval has passed (hence checking the date).
Chris
ASKER
Event 2502
The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include:
1) No zones are configured for scavenging by this server.
2) A scavenging cycle was performed within the last 30 minutes.
3) An error occurred during scavenging.
The next scavenging cycle is scheduled to run in 168 hours.
The event data will contain the error code if there was an error during the scavenging cycle.
For more information, see Help and Support Center at
Event 2501
The DNS server has completed a scavenging cycle:
Visited Zones = 1,
Visited Nodes = 17,
Scavenged Nodes = 1,
Scavenged Records = 0.
This cycle took 0 seconds.
The next scavenging cycle is scheduled to run in 168 hours.
The event data will contain the error code if there was an error during the scavenging cycle.
For more information, see Help and Support Center at
FYI I now have 40 more records rather than less records.
The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include:
1) No zones are configured for scavenging by this server.
2) A scavenging cycle was performed within the last 30 minutes.
3) An error occurred during scavenging.
The next scavenging cycle is scheduled to run in 168 hours.
The event data will contain the error code if there was an error during the scavenging cycle.
For more information, see Help and Support Center at
Event 2501
The DNS server has completed a scavenging cycle:
Visited Zones = 1,
Visited Nodes = 17,
Scavenged Nodes = 1,
Scavenged Records = 0.
This cycle took 0 seconds.
The next scavenging cycle is scheduled to run in 168 hours.
The event data will contain the error code if there was an error during the scavenging cycle.
For more information, see Help and Support Center at
FYI I now have 40 more records rather than less records.
ASKER
Is there a script to delete stale records that are static?
The two don't really fit together. Static records have a TimeStamp set to 0 normally, Stale have a time stamp, but it's older.
Are you finding that certain Stale Records are listed with a 0 Time Stamp? If so, how are you finding the values for the time stamp?
Chris
ASKER
All records so far have a time stamp and checked to delete when stale for 7 days. None of them deleted the last time 7 days cycled, even the test ones.
So what are the Aging Intervals set to?
The Scavenging period only dictates how frequently to run Scavenging, not whether or not the records are stale. It's why I normally recommend setting the Scavenging Period to 1 day. May as well keep it up to date.
Chris
ASKER
I read several EE discussion on scavaging and they warn never to set the cycle less that 4 days, so I set it at 4 days now. Also most records time stamps are very old , alot of them are year 2004,2006 etc.
Do they state a reason for that? Can't think of one myself because it does nothing more than act on the values set for Aging. Just curious :)
Anyway, that's not important. You still haven't said what you set the Aging intervals to, because those are important. We're still 2 days from 28th, if we last that long I would be interested to know the new value it sets for the next available for scavenging.
Chris
ASKER
OK, see you on the 28th
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'd still give Chris the points for all he did on this thread.
I completely agree with you mkline71, i too would still give chris the points for all his effort if it were me. It would also mean that this thread would remain for others to see.
I was following this thread on behalf of a friend/pre-colleague, which is how i came by. :)
I was following this thread on behalf of a friend/pre-colleague, which is how i came by. :)
pre-colleague...I like that Krys :)
Good point, this thread will help a lot of people in the future and since EE comes up on Google searches a lot that is a good thing.
Thanks
Mike
Good point, this thread will help a lot of people in the future and since EE comes up on Google searches a lot that is a good thing.
Thanks
Mike
Hey,
Would you be able to share your Aging settings? And how frequently you're running the Scavenging task?
Can you also check the "Next Available for Scavenging Time" on the zone by using View / Advanced, opening the Properties for the zone then looking at the date value at the bottom?
We can also report on which records that would be considered stale using a short script if that's of use.
Chris