Windows 2000 system ping nowhere cache is in trouble

Source: Computer Report

Windows 2000 automatically starts the DNS Client service, which provides the client's name resolution and caching service, and the user's DNS query results are cached locally. When configuring the DNS server, if you do not master this principle well, there will often be some erroneous operations.

Error operation, domain name is not available

The network where the author is located is a network directly connected by two machines. Both machines are installed with Windows Server 2000 system, one of which has been upgraded to a domain controller. The IP address is set to "10.202.10.1"; the other directory does not have Active Directory installed, and its IP address is "10.202.10.2". When doing the DNS server configuration experiment, configure the domain controller machine as a DNS server and the other machine as a DNS client.

Suppose you want to set the host IP address corresponding to the domain name www.jgx.com to "10.202.10.2". There are many students in the process of configuring the DNS server, when adding the host record, often the host's IP address is mistaken or mistyped, such as "10.202.10.2" is converted to "10.202.100.2", so the domain name on the client Will ping nowhere. If you return to the DNS console for modification at this time, change the IP address to "10.202.10.2". After the command is executed, the ping command is executed again at the command prompt of the client. The IP address of the domain name is still the address of the previous modification, 10.202.100.2, and the ping fails.

Using the Command to Clear the Cache

We can use the command at the command prompt to clear the information in the DNS client cache. Execute the "Ipconfig/flushdns" command on the client, and after the drive prompt appears, execute the "ping www.jgx.com" command to solve the problem.

It is worth noting that in the "Administrative Tools" open the "Services" tool, find the "DNS Client" item, after stopping the service, the client will not cache the DNS query information, so in the DNS server The changes made on it are immediately reflected when the client re-queries.