DNS cache

This is a discussion about DNS cache in the Windows Networking category; There are two versions of DNS cache tweaks on the net. One is in form of a *. reg file or a copy-paste directions to create one, the other is in story telling registry editing form. Both of them lacks any serious descriptions about what excactly are those values doing.

Windows Networking 2246 This topic was started by ,


data/avatar/default/avatar15.webp

8 Posts
Location -
Joined 2003-06-22
There are two versions of DNS cache tweaks on the net. One is in form of a *.reg file or a copy-paste directions to create one, the other is in story telling registry editing form. Both of them lacks any serious descriptions about what excactly are those values doing. It's often added that "don't ask why, just tweak it" or something. But I want to know couse the problem is - those two versions are different and both ar quite popular too (so can't decide based on popularity) couse the vide spreaded copy-paste h4xx0r don't-ask-why webmasters don't bother to look what thei're pasting on their site <- I could be wrong.
 
Here's the two versions and I want to know which one is "THE ONE"
_______________________________________________________
1)
 
Windows Registry Editor Version 5.00
 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters]
"CacheHashTableBucketSize"=dword:00000001
"CacheHashTableSize"=dword:00000180
"MaxCacheEntryTtlLimit"=dword:0000fa00
"MaxSOACacheEntryTtlLimit"=dword:0000012d
 
2)
 
...go in the registry to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters and modify "CacheHashTableBucketSize" to 384. Don’t ask me why… Then find "CacheHashTableSize" and change that to 64000 for no apparent reason, modify "MaxCacheEntryTtlLimit" to 301, and then change the perfectly good "MaxSOACacheEntryTtlLimit" to a very inadequate value of 300...
 
________________________________________________________
 
Now the diferences:
 
"CacheHashTableBucketSize"=dword:00000001 - is in decimal 1 vs 384
"CacheHashTableSize"=dword:00000180 - is in decimal 384 vs 64000
"MaxCacheEntryTtlLimit"=dword:0000fa00 - is in decimal 64000 vs 301
"MaxSOACacheEntryTtlLimit"=dword:0000012d - is in decimal 301 vs 300
 
In those two versions values got changed to each other and 301 is spelled to 1 or something, I don't know, maybe You know.

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This subject has been archived. New comments and votes cannot be submitted.

Responses to this topic


data/avatar/default/avatar15.webp

8 Posts
Location -
Joined 2003-06-22
OP
Thanks, I've read that page allready and used those values waiting for confirmation just to make sure.

data/avatar/default/avatar01.webp

738 Posts
Location -
Joined 2002-12-11
I agree with APK .... experiment with the vaules that will work for your setup.
 
You could always setup a caching DNS server or Proxy/Caching server if you truly wanted an improvement.

data/avatar/default/avatar15.webp

8 Posts
Location -
Joined 2003-06-22
OP
Thanks for the replies, the second version truly works for me so I go with that.