1. oBdA90,170
2. zelron2263,020
3. mkline7160,115
4. dariusg49,870
5. leew39,774
6. tigermatt39,425
7. demazter39,082
8. Chris-Dent38,800
9. Mestha33,856
10. KCTS31,228
11. ChiefIT30,871
12. henjoh0929,112
13. dstewartjr25,850
14. ram_kerala23,200
15. SysExpert19,400
16. Americom16,100
17. RobWill15,665
18. bluntTony12,750
19. Paranorm...12,250
20. alanhardisty10,703
21. MightySW10,675
22. lnkevin10,414
23. bdesmond9,868
24. snusgubben9,850
25. PeteJTho...9,448

1. KCTS401,638
2. oBdA214,220
3. leew159,866
4. Chris-Dent132,420
5. tigermatt113,223
6. dariusg105,845
7. RobWill90,650
8. Jay_Jay7086,905
9. henjoh0985,297
10. Sembee79,451
11. toniur71,558
12. ChiefIT66,703
13. LauraEHu...64,043
14. zelron2263,020
15. mkline7160,515
16. Shift-358,300
17. SysExpert56,977
18. ryansoto45,199
19. rindi44,641
20. demazter39,082
21. Netman6638,380
22. sirbounty36,899
23. hypercat36,198
24. lnkevin34,654
25. Pber34,507

	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

06/26/2007 at 10:43PM PDT, ID: 22660409

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.4

Conflicting Microsoft recommendations for DNS scavenging - looking for third opinions

Asked by iistech in Windows 2000 Server, Active Directory, Domain Name Service (DNS)

Tags: dns, scavenging, time

We have a large environment with Microsoft DNS and Windows 2000 AD. Since we have some client-related issues due to reverse lookups (discovery, for example), we are trying to figure out what the correct scavenging time should be. We have received conflicting recommendations from Microsoft, so I was hoping someone with larger environment experience might want to chime in on their opinions on the optimal scavenging times for stale records. I'm happy to set it to one day, per the SMS guy's recommendations, however, I am a little worried about how that will affect network traffic when the records are getting renewed so frequently (for forwards and reverses). We have a lot of mobile clients that go between buildings.

We have over 17,000 records in our DNS forward zone, and maybe 20% need to be purged. We have scavenging turned on and set to the default 7 days, and 7 days. There are some issues with this, but it's mostly OK. On the reverse zones, however, we have many that don't have scavenging at all, and there are literally thousands and thousands of old pointer records. We have tons of subnets, so there could be 15,000 or more records that need to be scavenged.

I need enable scavenging on all the reverse zones, which I can probably script with DNSCMD. Again, my main concern, because I can find no docs on this, is the effect of the record renewals happening so frequently.

We have DC's with DNS all over the place - 55 in all. Maybe 5000 users, and maybe 8000 or 9000 workstations and servers.

We will probably not do scavenging, or at least maybe pick a different time period for scavenging on server nets. But for the client nets, we will probably go with a one day period.

Anyone have any thoughts on this? I'm curious to see what others have done.

Thanks.

Rob "I"

View the Solution FREE for 30 Days

20091111-EE-VQP-91

Conflicting Microsoft recommendations for DNS scavenging - looking for third opinions

Asked by iistech in Windows 2000 Server, Active Directory, Domain Name Service (DNS)

Tags: dns, scavenging, time

About this solution