Another example is where customers report that they cannot access your Web site. To determine whether missing or incorrect DNS records are responsible for the problem, you must verify that each DNS server that hosts records for the Web servers is accurate. If you have a small number of DNS servers and DNS records, you can use Nslookup.exe to quickly verify the DNS records. But it can be time-consuming to use Nslookup.exe to verify a large number of records that are hosted on many DNS servers.
As a third example, users can send e-mail, but do not receive e-mail. The mail might be stalled on the e-mail server, and maybe there is a problem with name resolution. To determine whether this is so, you must verify all the related DNS records on all the authoritative DNS servers. Depending on the size and complexity of the e-mail infrastructure, this can be a complex and time-consuming task.
By using the /ql option in DNSLint, you can quickly query a large number of records on many DNS servers. DNSLint reads instructions from a file that is specified by the /ql option. When DNSLint has verified that the file is a valid DNSLint input file, it runs the queries that are specified in the file and reports the results in an easy-to-read HTML report. Administrators can use this input file to specify which DNS servers to query and exactly which DNS records to search for on each server. The format of the input file is as follows:
Thereafter, lines indicate the queries to send to the specified DNS server. For example:
The first field in the line is the name you want to query. For example, www.reskit.com. The name is immediately followed by a comma. Leave no spaces on either side of the comma.
The second field follows the comma immediately after the name you want to query. The second field is the type of DNS record to query for. Microsoft supports the following DNS record types:
- a = Host
- ptr = Pointer
- cname = Alias
- mx = Mail Exchange
- srv = Service Location
The third field is the type of DNS query you want to send. This field immediately follows the comma that is after the type of record. The following query types are valid:
- r = recursive
- i = iterative
A fourth field is optional. If you append ",tcp" to the third field, DNSLint sends the specified query by using the TCP protocol instead of the default UDP protocol. Again, leave no spaces. Nothing must follow this fourth field if you use it.
For additional information about this functionality, see the documentation that is included with the DNSLint download.
The following file is available for download from the Microsoft Download Center:
Download the dnslint-v2.02.exe package now.
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
Номер статьи: 330105 — последний просмотр: 7 янв. 2008 г. — редакция: 1