dig is generally considered a more powerful tool than
nslookup, but in the course of a typical network administrator's day, the minor limitations of
nslookup are unlikely to be too much of a factor. Instead,
dig is often simply the tool of choice for DNS information and troubleshooting on UNIX, Linux, or Macintosh systems. Like
dig can be used to perform simple name resolution requests. The output from this process can be seen in the following listing:
; <<>> DiG 8.2 <<>> xyz.com ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUERY SECTION: ;; xyz.com, type = A, class = IN ;; ANSWER SECTION: xyz.com. 7h33m IN A 18.104.22.168 ;; AUTHORITY SECTION: xyz.com. 7h33m IN NS usrxdns1.ABC.com. xyz.com. 7h33m IN NS oldtxdns2.ABC.com. ;; Total query time: 78 msec ;; FROM: localhost.localdomain to SERVER: default -- 22.214.171.124 ;; WHEN: Sat Oct 16 20:21:24 2004 ;; MSG SIZE sent: 30 rcvd: 103
As you can see, dig provides a number of pieces of information in the basic outputmore so than
nslookup. There are three key areas of the output from which network administrators can gain information. These are the 'Answer Section,' the 'Authority Section,' and the last four lines of the output.
The Answer Section of the output provides the name of the domain or host being resolved, along with its IP address. The
A in the results line indicates the record type that is being resolved.
The Authority Section provides information on the authoritative DNS servers for the domain against which the resolution request was performed. This information can be useful in determining whether the correct DNS servers are considered authoritative for a domain.
The last four lines of the output show how long the name resolution request took to process and the IP address of the DNS server that performed the resolution. It also shows the date and time of the request, as well as the size of the packets sent and received.