Clever Use of commands to clear the cache

Windows 2000 automatically starts the DNS Client Service, which provides the Client name resolution and cache service. Your DNS query results are cached locally. When configuring a DNS server, if you do not have a good grasp of this principle, some incorrect operations will often occur.

Incorrect operation, domain name failure

The author's network is a network composed of two directly connected machines. Both machines are installed with the Windows Server 2000 system, one of which has been upgraded to the domain controller and the IP address is set to "10.202.10.1 "; the IP address of the other active directory is "10.202.10.2 ". During the DNS server configuration experiment, the domain controller machine is configured as the DNS server, and the other machine is used as the DNS Client.

Assume that the Host IP address corresponding to the domain name www.jgx.com is "10.202.10.2 ". When adding host records, many students often mistake or lose the IP address of the host When configuring the DNS server. For example, they change "10.202.10.2" to "10.202.100.2 ", in this way, the domain name on the client cannot be pinged. If you go back to the DNS console to modify the IP address, change it to "10.202.10.2 ". After the Ping command is executed again at the command prompt on the client, the IP address resolved by the domain name is still the address "10.202.100.2" before the modification, and the Ping will still fail.

Use commands to clear Cache

You can use the command at the command prompt to clear the information in the DNS client cache. Run the "Ipconfig/flushdns" command on the client and run the "ping www.jgx.com" command to solve the problem.

It is worth noting that, open the "service" tool in "Administrative Tools" and find the "DNS Client" item. After the service is stopped, the DNS query information will not be cached on the Client, in this way, the modifications made on the DNS server can be immediately reflected when the client re-queries.