Advertisement

06.30.2008 at 07:28AM PDT, ID: 23526973
[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!

9.8

Scavenge Stale DNS Records?

Asked by twcadmin in Domain Name Service (DNS), Windows 2003 Server, Dynamic Host Configuration Protocol (DHCP)

Tags: , , ,

When I ping a client, it returns the incorrect ip address. I know this is caused by stale dns records but I want to prevent this in the future. It is an Active Director integrated zone on my windows server 2003 network and I want to enable "Scavenge stale resource records" but I want to know if there are any complications I should look out for before enabling this. I have static ip clients and DHCP clients. DHCP is set to a 4 hour DHCP lease with configured to "Always dynamically update DNS A and PTR records."

For scavenging, I was going to set no-refresh interval for 4 hours and refresh interval of 5 hours. Does this sound ok? Will there be any issues with static clients dns records being removed completely since they do not use DHCP? I guess I need a quick explanation of how dns scavenging works as well. Any other tips are much appreciated.Start Free Trial
[+][-]06.30.2008 at 08:05AM PDT, ID: 21899786

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Domain Name Service (DNS), Windows 2003 Server, Dynamic Host Configuration Protocol (DHCP)
Tags: Microsoft, Active Directory DNS, Windows 2003, Active Directory Stale DNS records, savenging, aging
Sign Up Now!
Solution Provided By: Chris-Dent
Participating Experts: 1
Solution Grade: A
 
 
[+][-]06.30.2008 at 11:48AM PDT, ID: 21901870

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]06.30.2008 at 12:08PM PDT, ID: 21902073

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628