6,868
社区成员
发帖
与我相关
我的任务
分享请发表友善的回复…
发表回复
乘思者 2005-04-04
- 打赏
- 举报
非常感谢！
icuc88 2005-03-28
- 打赏
- 举报
http://searchwinsystems.techtarget.com/tip/1,289483,sid68_gci1039955,00.html
Change the Windows 2000 DNS cache
DESKTOP MANAGEMENT
Change the Windows 2000 DNS cache
Serdar Yegulalp
21 Aug 2002
Rating: --- (out of 5)
Windows 2000 machines all have a client-side DNS cache that keeps local copies of DNS information. This allows sites to be loaded slightly faster, without having to perform a DNS lookup each time an address is needed. A DNS entry will stay in the cache until its TTL (Time to Live) value expires; another request after that point will force a new lookup.
If a given system is used to visit a broad variety of sites, whether it's a workstation or a server, you may want to set the size of the DNS cache to better accommodate that level of traffic.
Run REGEDT32 and browse to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesDnscacheParameters.
Create or modify the following REG_DWORD keys, and set their values as listed:
CacheHashTableBucketSize -- 384
CacheHashTableSize -- 64000
MaxCacheEntryTtlLimit -- 301
MaxSOACacheEntryTtlLimit -- 300
The CacheHashTable parameters are used to control the maximum number of columns in the hash table used by the DNS caching resolver service; the more columns, the faster the cache lookup, although this takes slightly more RAM.
MaxSOACacheEntryTtlLimit is the longest amount of time, in seconds, the cache holds any SOA (Start of Authority) records. Because SOA records are some of the most important DNS records, they cannot be held for too long, but you can force how long they are held with this value.
MaxCacheEntryTtlLimit is, in seconds, the upper limit for any cache entry's TTL value, and it overrides any value that may have been set on a specific record that is larger. If you set this value to 1, you can force DNS to perform a lookup on every query, which in effect disables the cache -- a useful value if you are performing any debugging.
You can also dump the contents of the DNS cache to the console with the command ipconfig /displaydns, and manually empty the cache with ipconfig /flushdns (again, useful for debugging or tracing problems with DNS).
Change the Windows 2000 DNS cache
DESKTOP MANAGEMENT
Change the Windows 2000 DNS cache
Serdar Yegulalp
21 Aug 2002
Rating: --- (out of 5)
Windows 2000 machines all have a client-side DNS cache that keeps local copies of DNS information. This allows sites to be loaded slightly faster, without having to perform a DNS lookup each time an address is needed. A DNS entry will stay in the cache until its TTL (Time to Live) value expires; another request after that point will force a new lookup.
If a given system is used to visit a broad variety of sites, whether it's a workstation or a server, you may want to set the size of the DNS cache to better accommodate that level of traffic.
Run REGEDT32 and browse to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesDnscacheParameters.
Create or modify the following REG_DWORD keys, and set their values as listed:
CacheHashTableBucketSize -- 384
CacheHashTableSize -- 64000
MaxCacheEntryTtlLimit -- 301
MaxSOACacheEntryTtlLimit -- 300
The CacheHashTable parameters are used to control the maximum number of columns in the hash table used by the DNS caching resolver service; the more columns, the faster the cache lookup, although this takes slightly more RAM.
MaxSOACacheEntryTtlLimit is the longest amount of time, in seconds, the cache holds any SOA (Start of Authority) records. Because SOA records are some of the most important DNS records, they cannot be held for too long, but you can force how long they are held with this value.
MaxCacheEntryTtlLimit is, in seconds, the upper limit for any cache entry's TTL value, and it overrides any value that may have been set on a specific record that is larger. If you set this value to 1, you can force DNS to perform a lookup on every query, which in effect disables the cache -- a useful value if you are performing any debugging.
You can also dump the contents of the DNS cache to the console with the command ipconfig /displaydns, and manually empty the cache with ipconfig /flushdns (again, useful for debugging or tracing problems with DNS).
icuc88 2005-03-28
- 打赏
- 举报
本地的还是服务器端的？
hzy111 2005-03-28
- 打赏
- 举报
接分
cmk65 2005-03-28
- 打赏
- 举报
楼主想通过什么方法解决？
乘思者 2005-03-28
- 打赏
- 举报
很感谢，不过好像不是这个问题。
YE0515 2005-03-25
- 打赏
- 举报
http://www.douzhe.com/docs/jh/4/336646.html
乘思者 2005-03-23
- 打赏
- 举报
不是的吧，我记得不知道在什么地方看到，本机缓存最后十条DNS解析的结果。
就算不是的话，那会是什么原因呢？该怎么解决？
Re： oyljerry 不可能经常这样闪短把。再说，又不知是用了一个DNS服务器。
re: 这个不会，访问其他的网站是正常的。
谢谢，以上各位，都会有分的，希望大家多多关注，来者有分。
就算不是的话，那会是什么原因呢？该怎么解决？
Re： oyljerry 不可能经常这样闪短把。再说，又不知是用了一个DNS服务器。
re: 这个不会，访问其他的网站是正常的。
谢谢，以上各位，都会有分的，希望大家多多关注，来者有分。
alx0614 2005-03-18
- 打赏
- 举报
网络问题，网卡或宽带
oyljerry 2005-03-18
- 打赏
- 举报
可能DNS服务器服务
sheerfish999 2005-03-18
- 打赏
- 举报
这未必和 DNS解析缓存数量 有关系吧？
