The client resolver cache is the first place that the DNS client looks for host name resolution. Because it is a location in memory, the client resolver cache resolves IP addresses more quickly than the other host name resolution methods and does not create network traffic. The cache stores host names that have recently been resolved. It also contains mappings that are loaded from the Hosts file. These mappings include the record name, Time-to-Live (TTL) value, and IP address.
Resolver
If this for a DNS server, use the command "dnscmd" with options. eg: dnscmd dnssvr1.contoso.com /clearcache To clear DNS Cache in client, do the following: 1. Start 2. Run 3. Type "cmd" and press enter 4. In the command window type "ipconfige /flushdns" 5.a If done correctly it should say "Successfully flushed the DNS Resolver Cache." 5.b If you receive an error "Could not flush the DNS Resolver Cache: Function failed during execution.", follow the Microsoft KB Article 919746 to enable the cache. The cache will be empty; however, this will allow successful cache-flush in future.
ipconfig /flushdns
In Microsoft Windows Server 2003, you run the ipconfig /displaydns command to display the content of the DNS resolver cache. However, the results are incomplete. When this problem occurs, you do not receive a message.This problem occurs if there are too many entries in the DNS resolver cache. Typically, this problem occurs when there are too many custom entries in the Hosts file.This problem occurs when an allocated buffer is not large enough to contain all the contents of the DNS resolver cache. When the Ipconfig.exe tool allocates memory, it does not consider the DNS entries in the Hosts file.LINK Below
If you mean the DNS Resolver Cache, Windows XP Users can "clear" this cache by clicking on the "start" button, click, "run" and enter "cmd" in the box. a new window will appear with a black background. In this window, enter, "ipconfig/flushdns" (without the quotes) and hit Enter. You should get a prompt that states, "Successfully Flushed The DNS Resolver Cache". This should speed up your internet browsing a little bit.
Cache,Host Files, DNS server
The client side of a Domain Name System (DNS) is called a DNS Resolver. It is responsible for initiating the queries that lead to the full resolution of the translation of a domain name into an IP address. A small amount of DNS Resolvers only communicate to one single server instead of multiple servers.
If a client send a query requesting for a particular web page to the DNS server and if the DNS server resolves the page from the other DNS servers & it will be store the same page in the DNS cache and it will give the response to the client with the requested page. If again the same web page is requested by any client then DNS server will get the web page from the DNS cache instead of again fetching the same page from the internet. With this there wont be any delay for the client to get the web page. This helps in bandwidth control. This is how the DNS server caching works.
op
Local DNS cache of client computer, then the hosts file on the local PC finally going to the assigned DNS servers the computer is pointing to
start -run ipconfig /flushdns
An iterative name query is one in which a DNS client allows the DNS server to return the best answer it can give based on its cache or zone data. If the queried DNS server does not have an exact match for the queried name, the best possible information it can return is a referral (that is, a pointer to a DNS server authoritative for a lower level of the domain namespace). The DNS client can then query the DNS server for which it obtained a referral. It continues this process until it locates a DNS server that is authoritative for the queried name, or until an error or time-out condition is met.This process is sometimes referred to as "walking the tree," and this type of query is typically initiated by a DNS server that attempts to resolve a recursive name query for a DNS client.