debian/djbdns-man/dnstrace.1

   1 .TH dnstrace 1
   2
   3 .SH NAME
   4 dnstrace \- dns lookup tool
   5
   6 .SH SYNOPSIS
   7 .B dnstrace
   8 .I t
   9 .I fqdn
  10 .I r
  11
  12 .SH DESCRIPTION
  13 .B dnstrace
  14 searches for all DNS servers
  15 that can affect the resolution of records of type
  16 .I t
  17 under the domain name
  18 .IR fqdn ,
  19 starting from the root server
  20 .IR r .
  21 You can list more than one root server.
  22
  23 .B dnstrace
  24 uses the standard DNS resolution algorithm,
  25 but follows all possible paths in the algorithm.
  26 It prints all responses it receives from DNS servers;
  27 it also prints warnings about slow servers, dead servers,
  28 misdelegated (``lame'') servers, and misformatted packets.
  29 .B dnstrace
  30 is similar in spirit to DOC and dnswalk
  31 but is much more effective than those tools at debugging resolution problems.
  32
  33 In versions 1.03 and above:
  34 You can pipe
  35 .B dnstrace
  36 through
  37 .BR dnstracesort (1)
  38 for human-friendly output.
  39 .B dnstrace
  40 can take a long time to run,
  41 so standard procedure is to save its output in a file:
  42
  43   dnstrace any www.aol.com a.root-servers.net > AOL &
  44
  45 Then you can run
  46 .BR dnstracesort (1)
  47 to see the results so far:
  48
  49   dnstracesort < AOL | less
  50
  51 The
  52 .BR dnstracesort (1)
  53 output uses
  54 .I ul
  55 codes
  56 for boldface and underline;
  57 these codes are displayed properly by
  58 .BR less (1).
  59
  60 Beware that, as of January 2001,
  61 .B dnstrace
  62 produces more than 5 megabytes of output
  63 for the complete trace of cr.yp.to
  64 starting from all the root servers.
  65 It ends up sending more than 6000 queries to more than 200 different servers.
  66
  67 .SH SEE ALSO
  68 dnsip(1),
  69 dnsipq(1),
  70 dnsmx(1),
  71 dnstxt(1),
  72 dnsqr(1),
  73 dnsq(1),
  74 dnsname(1),
  75 less(1),
  76 tinydns-get(1)
  77
  78 http://cr.yp.to/djbdns.html