Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

November 22, 2005 12:00 AM

Controlling Positive and Negative Caching

Windows IT Pro
InstantDoc ID #48528
Rating: (0)

Controlling Positive and Negative Caching
Windows caching occurs according to default time periods, depending on which version of Windows you're using and how it's configured. You can control this caching behavior by manipulating the values of two registry keys. The HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNSCache\Parameters subkey holds the values, which let you adjust the length of time that positive and negative responses are stored in the cache. These values are slightly different in Windows Server 2003, Windows XP, and Windows 2000.

For positive caching in Win2K, the value is MaxCacheEntryTtlLimit , and in XP and Windows 2003 the value is MaxCacheTtl . Each value refers to the maximum number of seconds that a positive DNS response should be stored in cache. If the key exists on your system, the default value is likely 86,400 seconds (1 day). This value will override any TTL values provided in a DNS response that might be greater; therefore, the maximum time that Windows will cache a positive response (by default) is 1 day, even if the TTL in the response is set for 5 days. By setting this value to 1 second, you can effectively negate the effects of positive caching of DNS lookups on your system.

For negative-response caching in Win2K, the value is NegativeCacheTime , and in XP and Windows 2003, the value is MaxNegativeCacheTtl . The default value is 300 seconds (5 minutes) in Win2K and 900 seconds (15 minutes) in XP and Windows 2003. Negative responses returned from a DNS server will be cached for this time interval, and any future queries—even if a host suddenly has a valid record where it didn't before—will fail with a negative response until the cache timer runs out. As you're bringing new systems online, negative caching can definitely be troublesome if you attempt to resolve the name before it's available on the network.

You can find more information about these procedures in the Microsoft articles “How to Disable Client-Side DNS Caching in Windows 2000” (http://support.microsoft.com/default.aspx?scid=kb;en-us;245437) and “How to Disable Client-Side DNS Caching in Windows XP and Windows Server 2003” (http://support.microsoft.com/default.aspx?scid=kb;en-us;318803).

Related Content:

ARTICLE TOOLS

Comments
    There are no comments to display. Be the first one!
You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.