Technical data

Configuring and Managing BIND
5.8 Using NSLOOKUP to Query a Name Server
> ls -m lgk.sea.com
brigit 12H IN MX 10 brigit
12H IN MX 100 mail1.digital.com.
12H IN MX 100 mail2.digital.com.
12H IN MX 200 crl.SEA.com.
piglet 12H IN MX 10 piglet
12H IN MX 100 mail1.digital.com.
12H IN MX 100 mail2.digital.com.
12H IN MX 200 crl.SEA.com.
tieta 12H IN MX 10 tieta
12H IN MX 100 mail1.digital.com.
12H IN MX 100 mail2.digital.com.
12H IN MX 200 crl.SEA.com.
sherry 12H IN MX 10 sherry
12H IN MX 100 mail1.digital.com.
12H IN MX 100 mail2.digital.com.
12H IN MX 200 crl.SEA.com.
In the following example, using the -s option displays the well-known services for
a domain.
> ls -s lgk.sea.com
[condor.lgk.sea.com]
WKStesthave 12H IN WKS 16.99.208.255 21 ( )
WKStesthavenot 12H IN WKS 16.99.208.255 255 ( )
WKStestnumbers 12H IN WKS 16.99.208.255 255 ( 21 23 )
You can redirect the output from this command to a file. This method is helpful
when the domain consists of a large number of hosts. Once the file is created, you
can look at its contents with the DCL command TYPE. For example:
> ls -t a klg.sea.com > systems.txt
[condor.klg.sea.com]
#############
Received 932 answers (0 records).
$ TYPE SYSTEMS.TXT
> ls -t a klg.sea.com
[condor.klg.sea.com]
$ORIGIN KLG.SEA.COM.
@ 12H IN A 16.99.208.208
dhcp-253 12H IN A 16.99.208.253
ucxv4a 12H IN A 16.99.208.129
beavis 12H IN A 16.99.208.90
boxmor 12H IN A 16.99.208.30
kempo 12H IN A 16.99.208.47
pacnet 12H IN A 16.99.208.84
kwai 12H IN A 16.99.208.63
alxica 12H IN A 16.99.9.37
ppponvms 12H IN A 16.99.208.104
5.9 Solving Bind Server Problems
To solve BIND server problems, refer to the following sections:
• Section 5.9.1, Server Not Responding
• Section 5.9.2, Serial Number Mismatch
Configuring and Managing BIND 5–47