Win2k "secret weapon" DNS tool (1)

Tools for use in a network environment: Great for those who work as maintainers. And need to pay attention: some tools need another tool as a basis to use, that is, when a tool is working, another tool as a basis must be executed first. These tools are:

Remote File Storage Diagnostics

Remote File Storage Analysis

Distributed File System Utilities

Distributed File System Due to Increasing Network Popularity More and more applications are being used, and the use of tools based on the network to troubleshoot is increasing. For those friends who need to deal with the Internet frequently, this part must be seen.

Web-based tools are not just these. Windows 2000's resource tools are equipped with quite a bit of this kind of software -- the network management tool that will be introduced below. There are 16 tools in this series:

The name of the executable corresponding to the tool name

ADSI Edit Operation Console

DNS Server Troubleshooting Tool (Dnscmd. Exe)

DsAcls (Dsacls.exe)

DsaStat (Dsastat.exe)

Kerberos Setup (Ksetup.exe)

Kerberos Keytab Setup (Ktpass .exe)

Active Directory Administration Tool (Ldp.exe)

Active Directory Object Manager (Movetree.exe)

Windows 2000 Domain Manager (Netdom.exe)

NlTest (Nltest.exe)

Remote Command Line (Remote.exe)

Replication Diagnostics Tool (Repadmin.exe)

Active Directory Repl Ication Monitor (Replmon.exe)

Security Descriptor Check Utility (Sdcheck.exe)

Active Directory Search Tool (Search.vbs)

Winsock Remote Console (Wsremote.exe )

Because these tools are network-based or used in a networked environment, there are very few people who really have the opportunity to practice, compared to the personal computer environment. But whether any technology can develop or not depends on its vitality. Nowadays, the popularity of the network has brought tremendous vitality to the popularization of network technology. Maintaining this technological advantage of simultaneous popularization is the strategy for winning in the future.

I have sorted out these materials, one for learning and the other for sharing with you. Everything is so sincere, so I hope that if you find something wrong, you must criticize and correct it, and you will not be willing to be sincere.

DNS Server Troubleshooting Tool

The English full name of this tool is: DNS Server Troubleshooting Tool, which is used to troubleshoot the domain name service system, abbreviated as: DNScmd. This is a tool for system administrators to use in the Domain Name Service (DNS). The form of the tool is based on the command line. With this tool, system administrators can observe the properties, scope, and resource records of the domain name service system. In addition, this tool allows you to modify the above attributes in manual form, that is, you can create or delete resource records, or force event copying between the domain server's physical memory and the domain name service database and data files.

In Windows NT, a tool related to this is called: Dnsstat.exe (found in the Windows NT Resource Kit), and DNScmd.exe is an enhanced version of the former.

As mentioned above: This is a command line tool. For command line programs, you need to run the command console CMD first. Since the use of CMD has already been introduced in the previous article, there is no longer any explanation here. In the following sections, assume that you have opened the command console.

Usage of DNScmd.exe

If you want to get help from DNScmd.exe, you can use DNScmd/? The command form takes the details of the help; DNScmd.exe contains a lot of commands. If you want to get help with a specific command, you can use this form: Dnscmd command /? , where command is the name of a command specified (see below for details), the space before the command can not be omitted.

I verified on my own machine. After running CMD, type dnscmd/at the system prompt. And then press Enter, which is shown below. Considering the space limit, the place with the ellipsis in the middle is the omitted item:

Microsoft Windows 2000 [Version 5.00.2195]

(C Copyright 1985-1998 Microsoft Corp.

C:>dnscmd/?

USAGE: DnsCmd []

:

. -- local machine using LPC

IP address -- RPC over TCP/IP

DNS name -- RPC over TCP/IP

other server name -- RPC over named pipes

:

/Info -- Get server information

……

/ResetForwarders -- Set DNS servers to forward recursive queries to

/ZoneInfo -- View zone information

……

/ZoneResetMasters -- Reset secondary zone's master servers

/EnumRecords -- Enumerate records at a name

/RecordAdd -- Create a record in zone or RootHints

/RecordDelete -- Delete a record from zone, RootHints or Cache d

ata

/NodeDelete -- Delete all records at a name

/AgeAllRecords -- Force aging On node(s) in zone

:

-- parameters specific to each Command

dnscmd /? -- For help info on specific Command

C:>

Compared to the official help documentation, the help tips here are very simple. But the most important finding is that the total number of commands provided by the two is not the same. This is not the first time that this formal help document and online prompts are inconsistent. Where is the difference, when introducing the relevant orders, I will remind you.

Because Windows 2000 attaches great importance to security issues, tools like this that modify important attributes must also perform permission verification on the user of the tool. Users who do not log in to the system correctly may not use this. tool. In other words, this tool can only be used by properly trusted users who have already been trusted. It seems complicated, but in fact, as long as you can log in to Windows 2000 as a system administrator, you can use it in the command console.

Command usage:

All Dnscmd.exe commands have a uniform form. See the next line:

dnscmd ServerName Command [Command Parameters]

The complete command syntax is divided into four parts: dnscmd is the name of the tool and cannot be omitted.

ServerName is the server name and cannot be omitted.

The command specified by Command cannot be omitted.

The Command Parameters command parameter is an optional item.

These four parts:

A : The name of the tool (program) is not to be said, it is used directly;

B: The server name is managed by the system. The name of the machine that is planned for management. Here, the server name is used as a variable. Since it is a variable, it must be replaced by the specific value when it is actually executed. The following items are replaced by the server name:

1. The specified local computer works with local connection access. Local connection access is abbreviated in English as: LPC

2. Using an IP address, the format of the IP address is: xx.xx.xx.xx. Specify the DNS server, which needs to use the remote connection access method via TCP/IP. Remote connection access is abbreviated in English as: RPC.

3. The specified DNS name: this name must be a complete, qualified (authenticated) DNS server name (ie FQDN), and work needs to be via TCP/IP, using remote connection access. .

4. NetBIOS Name: Similar to the previous one, it is based on NetBIOS and not via TCP/IP. Work also needs to use remote connection access.

C : Command command

Command is the name of the command. This tool has many commands, and different commands have different functions. For details, please refer to the following introduction.

D: Command Parameters

Optional items at this time, some commands may not have parameters.

At this point, we have completed all the preparatory work for using this tool. Beginning with the next article, we will introduce the syntax, usage, and example analysis of each command.