Server Management Maintenance: Clear DNS Cache_About the server

Server Management Maintenance: Clear DNS Cache

  

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.

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.webjx.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.

-------------------------------------------- -------------------------------------------------< Br>

When there is a problem with domain name resolution, the DNS server may update the IP address of this domain name, but it does not correspond to the information stored in the local DNS cache. As a result, there is a problem with domain name resolution. DNS local cache, simply clear the local DNS local cache.
1, enter cmd in the run, then enter ipconfig /flushdns.

2. Stop the DNS CLIENT service in the system service, and you can not store the DNS query information locally.

3, close IE, then clear the history or restart the machine.

The three methods can correctly resolve the domain name immediately. Sharing ODBC Connections Between Users
Windows 2000 supports Open Database Connectivity (ODBC), a standard mechanism developed by Microsoft that enables customers to access databases created by various database management systems without having to install a DBMS locally.


For example, you can create an ODBC connection on a server to access a product database from the Web. Web pages with IIS as the host system can contain the necessary calls to access ODBC connections and underlying data.

Windows 2000 supports three ODBC data source names (DSNs): systems, users, and files. The Windows 2000 system and user DSN are stored in the registry. The file DSN is a file with a .dsn extension.

The general use of file DSNs is to provide database connections for local applications, such as Excel or Access. The advantage of using a folder DSN is that you can easily share it between users, sharing or copying DSN files to each user's computer over a network.

To share a file DSN between users, first create a DSN using the Data Source applet under the Administrative Tools applet in Control Panel, and then place the DSN in a location that the user can access. Users must add the DSN folder path to their corresponding application settings.

For example, if users use Excel, select data| Import external data| Create a new database query. In the Select Data Source dialog box, click Options, enter the path to the shared DSN folder, and then click to close the dialog box. Then other users can use the DSN in the application.

Use scavenging to clear DNS
Windows 2000's DNS service supports the scavenging feature, which helps you keep the DNS records managed by the service up to date. Scavenging is quite important if you use dynamic DNS to automatically register their hostnames after the client's IP address changes. This happens as much as the client automatically obtains an IP address via DHCP.

Over time, client host records in an area may be outdated and scavenging deletes those records. Deleting records improves DNS server and zone transfer performance, and it also ensures that host records are not old record conflicts.

You can configure scavenging through the properties of a region. Open the DNS console, right click on Zone and select Properties. On the General tab, click Aging to open the Zone Aging/Scavenging Properties dialog. Use the drop-down list box to set the Refresh Interval and Non-refresh Interval, select the Scavenge Stale Resource Records checkbox, and click OK to close both dialogs.

You can also configure scavenging for the entire region by editing the properties of the server instead of configuring a single region. In the DNS console, right click on the server and select Set Aging/Scavenging For All Zones. The dialog box that pops up is the same as the one that configures a single area.


Delegate a Policy Group Object
Use Ipconfig to Observe and Manage DNS Resolution Cache
DNS Clients on Windows2000 Professional Platform Resolve Hostnames to IP Addresses, and Other Windows Operations The platform is the same. DNS resolution requires support for web browsers, as well as support for mail services and other applications that rely on hostnames rather than IP addresses.


Windows DNS resolution stores DNS query results, including affirmative queries, and of course negative queries (parsing failed queries).

Each DNS record has a time-to-live (TTL) value that determines when the record is refreshed and replaced by other queries. Before the TTL arrives, Windows parsing will return the results of the query in the cache without starting a new query.


When you want to solve the problem of connection and DNS, it is necessary to clear the DNS cache and force Windows to perform a new resolution on a hostname. You can use the IPConfig console command to observe the cache size and clear the cache.


The cached capacity can be displayed by the following command, and the result is sent to the More command, so that the result is displayed on one page at a time:
ipconfig /displaydns |  More


Use this command to empty the cache:

ipconfig /flushdns

Delegating a Policy Group Object
With the expansion of the network, especially in When you need to manage policy groups across different departments or regions, you will find it increasingly difficult to manage servers and networks. Delegate control of Strategic Group Control Objects (GPOs) can help with your management simplification. The commissioned administrator can manage the policy group with a special organizational unit (Ous) or domain as needed.


Entrust GPO management to set the GPO access control list to control user read/write access. The specific steps are as follows:

1. Open Active Directory Users and Computer Console

2. Right click on the OU connected to the GPO, expand the domain, select properties;

3. Click on the strategy group label, select the GPO, then click on Properties;

4. Click on the security label to add the group or user to whom the GPO was delegated, and both choose to allow read and write operations;

5. Click the OK button to close the GPO property bar, then press the OK button to close the OU's property bar;