PageRenderTime 74ms CodeModel.GetById 31ms app.highlight 33ms RepoModel.GetById 1ms app.codeStats 0ms

/contrib/bind9/bin/dig/dig.html

https://bitbucket.org/freebsd/freebsd-head/
HTML | 645 lines | 621 code | 7 blank | 17 comment | 0 complexity | ef433ec2bc0e78b971b1cf11c92a2e8f MD5 | raw file
  1<!--
  2 - Copyright (C) 2004-2010 Internet Systems Consortium, Inc. ("ISC")
  3 - Copyright (C) 2000-2003 Internet Software Consortium.
  4 - 
  5 - Permission to use, copy, modify, and/or distribute this software for any
  6 - purpose with or without fee is hereby granted, provided that the above
  7 - copyright notice and this permission notice appear in all copies.
  8 - 
  9 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
 10 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
 11 - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
 12 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
 13 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
 14 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
 15 - PERFORMANCE OF THIS SOFTWARE.
 16-->
 17<!-- $Id$ -->
 18<html>
 19<head>
 20<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 21<title>dig</title>
 22<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
 23</head>
 24<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en">
 25<a name="man.dig"></a><div class="titlepage"></div>
 26<div class="refnamediv">
 27<h2>Name</h2>
 28<p>dig &#8212; DNS lookup utility</p>
 29</div>
 30<div class="refsynopsisdiv">
 31<h2>Synopsis</h2>
 32<div class="cmdsynopsis"><p><code class="command">dig</code>  [@server] [<code class="option">-b <em class="replaceable"><code>address</code></em></code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-f <em class="replaceable"><code>filename</code></em></code>] [<code class="option">-k <em class="replaceable"><code>filename</code></em></code>] [<code class="option">-m</code>] [<code class="option">-p <em class="replaceable"><code>port#</code></em></code>] [<code class="option">-q <em class="replaceable"><code>name</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-x <em class="replaceable"><code>addr</code></em></code>] [<code class="option">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]name:key</code></em></code>] [<code class="option">-4</code>] [<code class="option">-6</code>] [name] [type] [class] [queryopt...]</p></div>
 33<div class="cmdsynopsis"><p><code class="command">dig</code>  [<code class="option">-h</code>]</p></div>
 34<div class="cmdsynopsis"><p><code class="command">dig</code>  [global-queryopt...] [query...]</p></div>
 35</div>
 36<div class="refsect1" lang="en">
 37<a name="id2543524"></a><h2>DESCRIPTION</h2>
 38<p><span><strong class="command">dig</strong></span>
 39      (domain information groper) is a flexible tool
 40      for interrogating DNS name servers.  It performs DNS lookups and
 41      displays the answers that are returned from the name server(s) that
 42      were queried.  Most DNS administrators use <span><strong class="command">dig</strong></span> to
 43      troubleshoot DNS problems because of its flexibility, ease of use and
 44      clarity of output.  Other lookup tools tend to have less functionality
 45      than <span><strong class="command">dig</strong></span>.
 46    </p>
 47<p>
 48      Although <span><strong class="command">dig</strong></span> is normally used with
 49      command-line
 50      arguments, it also has a batch mode of operation for reading lookup
 51      requests from a file.  A brief summary of its command-line arguments
 52      and options is printed when the <code class="option">-h</code> option is given.
 53      Unlike earlier versions, the BIND 9 implementation of
 54      <span><strong class="command">dig</strong></span> allows multiple lookups to be issued
 55      from the
 56      command line.
 57    </p>
 58<p>
 59      Unless it is told to query a specific name server,
 60      <span><strong class="command">dig</strong></span> will try each of the servers listed
 61      in
 62      <code class="filename">/etc/resolv.conf</code>.
 63    </p>
 64<p>
 65      When no command line arguments or options are given,
 66      <span><strong class="command">dig</strong></span> will perform an NS query for "." (the root).
 67    </p>
 68<p>
 69      It is possible to set per-user defaults for <span><strong class="command">dig</strong></span> via
 70      <code class="filename">${HOME}/.digrc</code>.  This file is read and
 71      any options in it
 72      are applied before the command line arguments.
 73    </p>
 74<p>
 75      The IN and CH class names overlap with the IN and CH top level
 76      domains names.  Either use the <code class="option">-t</code> and
 77      <code class="option">-c</code> options to specify the type and class, 
 78      use the <code class="option">-q</code> the specify the domain name, or
 79      use "IN." and "CH." when looking up these top level domains.
 80    </p>
 81</div>
 82<div class="refsect1" lang="en">
 83<a name="id2543597"></a><h2>SIMPLE USAGE</h2>
 84<p>
 85      A typical invocation of <span><strong class="command">dig</strong></span> looks like:
 86      </p>
 87<pre class="programlisting"> dig @server name type </pre>
 88<p>
 89      where:
 90
 91      </p>
 92<div class="variablelist"><dl>
 93<dt><span class="term"><code class="constant">server</code></span></dt>
 94<dd><p>
 95              is the name or IP address of the name server to query.  This can
 96              be an IPv4
 97              address in dotted-decimal notation or an IPv6
 98              address in colon-delimited notation.  When the supplied
 99              <em class="parameter"><code>server</code></em> argument is a
100              hostname,
101              <span><strong class="command">dig</strong></span> resolves that name before
102              querying that name
103              server.  If no <em class="parameter"><code>server</code></em>
104              argument is provided,
105              <span><strong class="command">dig</strong></span> consults <code class="filename">/etc/resolv.conf</code>
106              and queries the name servers listed there.  The reply from the
107              name
108              server that responds is displayed.
109            </p></dd>
110<dt><span class="term"><code class="constant">name</code></span></dt>
111<dd><p>
112              is the name of the resource record that is to be looked up.
113            </p></dd>
114<dt><span class="term"><code class="constant">type</code></span></dt>
115<dd><p>
116              indicates what type of query is required &#8212;
117              ANY, A, MX, SIG, etc.
118              <em class="parameter"><code>type</code></em> can be any valid query
119              type.  If no
120              <em class="parameter"><code>type</code></em> argument is supplied,
121              <span><strong class="command">dig</strong></span> will perform a lookup for an
122              A record.
123            </p></dd>
124</dl></div>
125<p>
126    </p>
127</div>
128<div class="refsect1" lang="en">
129<a name="id2543688"></a><h2>OPTIONS</h2>
130<p>
131      The <code class="option">-b</code> option sets the source IP address of the query
132      to <em class="parameter"><code>address</code></em>.  This must be a valid
133      address on
134      one of the host's network interfaces or "0.0.0.0" or "::".  An optional
135      port
136      may be specified by appending "#&lt;port&gt;"
137    </p>
138<p>
139      The default query class (IN for internet) is overridden by the
140      <code class="option">-c</code> option.  <em class="parameter"><code>class</code></em> is
141      any valid
142      class, such as HS for Hesiod records or CH for Chaosnet records.
143    </p>
144<p>
145      The <code class="option">-f</code> option makes <span><strong class="command">dig </strong></span>
146      operate
147      in batch mode by reading a list of lookup requests to process from the
148      file <em class="parameter"><code>filename</code></em>.  The file contains a
149      number of
150      queries, one per line.  Each entry in the file should be organized in
151      the same way they would be presented as queries to
152      <span><strong class="command">dig</strong></span> using the command-line interface.
153    </p>
154<p>
155      The <code class="option">-m</code> option enables memory usage debugging.
156      
157    </p>
158<p>
159      If a non-standard port number is to be queried, the
160      <code class="option">-p</code> option is used.  <em class="parameter"><code>port#</code></em> is
161      the port number that <span><strong class="command">dig</strong></span> will send its
162      queries
163      instead of the standard DNS port number 53.  This option would be used
164      to test a name server that has been configured to listen for queries
165      on a non-standard port number.
166    </p>
167<p>
168      The <code class="option">-4</code> option forces <span><strong class="command">dig</strong></span>
169      to only
170      use IPv4 query transport.  The <code class="option">-6</code> option forces
171      <span><strong class="command">dig</strong></span> to only use IPv6 query transport.
172    </p>
173<p>
174      The <code class="option">-t</code> option sets the query type to
175      <em class="parameter"><code>type</code></em>.  It can be any valid query type
176      which is
177      supported in BIND 9.  The default query type is "A", unless the
178      <code class="option">-x</code> option is supplied to indicate a reverse lookup.
179      A zone transfer can be requested by specifying a type of AXFR.  When
180      an incremental zone transfer (IXFR) is required,
181      <em class="parameter"><code>type</code></em> is set to <code class="literal">ixfr=N</code>.
182      The incremental zone transfer will contain the changes made to the zone
183      since the serial number in the zone's SOA record was
184      <em class="parameter"><code>N</code></em>.
185    </p>
186<p>
187      The <code class="option">-q</code> option sets the query name to 
188      <em class="parameter"><code>name</code></em>.  This useful do distinguish the
189      <em class="parameter"><code>name</code></em> from other arguments.
190    </p>
191<p>
192      Reverse lookups &#8212; mapping addresses to names &#8212; are simplified by the
193      <code class="option">-x</code> option.  <em class="parameter"><code>addr</code></em> is
194      an IPv4
195      address in dotted-decimal notation, or a colon-delimited IPv6 address.
196      When this option is used, there is no need to provide the
197      <em class="parameter"><code>name</code></em>, <em class="parameter"><code>class</code></em> and
198      <em class="parameter"><code>type</code></em> arguments.  <span><strong class="command">dig</strong></span>
199      automatically performs a lookup for a name like
200      <code class="literal">11.12.13.10.in-addr.arpa</code> and sets the
201      query type and
202      class to PTR and IN respectively.  By default, IPv6 addresses are
203      looked up using nibble format under the IP6.ARPA domain.
204      To use the older RFC1886 method using the IP6.INT domain
205      specify the <code class="option">-i</code> option.  Bit string labels (RFC2874)
206      are now experimental and are not attempted.
207    </p>
208<p>
209      To sign the DNS queries sent by <span><strong class="command">dig</strong></span> and
210      their
211      responses using transaction signatures (TSIG), specify a TSIG key file
212      using the <code class="option">-k</code> option.  You can also specify the TSIG
213      key itself on the command line using the <code class="option">-y</code> option;
214      <em class="parameter"><code>hmac</code></em> is the type of the TSIG, default HMAC-MD5,
215      <em class="parameter"><code>name</code></em> is the name of the TSIG key and
216      <em class="parameter"><code>key</code></em> is the actual key.  The key is a
217      base-64
218      encoded string, typically generated by
219      <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
220
221      Caution should be taken when using the <code class="option">-y</code> option on
222      multi-user systems as the key can be visible in the output from
223      <span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
224      or in the shell's history file.  When
225      using TSIG authentication with <span><strong class="command">dig</strong></span>, the name
226      server that is queried needs to know the key and algorithm that is
227      being used.  In BIND, this is done by providing appropriate
228      <span><strong class="command">key</strong></span> and <span><strong class="command">server</strong></span> statements in
229      <code class="filename">named.conf</code>.
230    </p>
231</div>
232<div class="refsect1" lang="en">
233<a name="id2544037"></a><h2>QUERY OPTIONS</h2>
234<p><span><strong class="command">dig</strong></span>
235      provides a number of query options which affect
236      the way in which lookups are made and the results displayed.  Some of
237      these set or reset flag bits in the query header, some determine which
238      sections of the answer get printed, and others determine the timeout
239      and retry strategies.
240    </p>
241<p>
242      Each query option is identified by a keyword preceded by a plus sign
243      (<code class="literal">+</code>).  Some keywords set or reset an
244      option.  These may be preceded
245      by the string <code class="literal">no</code> to negate the meaning of
246      that keyword.  Other
247      keywords assign values to options like the timeout interval.  They
248      have the form <code class="option">+keyword=value</code>.
249      The query options are:
250
251      </p>
252<div class="variablelist"><dl>
253<dt><span class="term"><code class="option">+[no]tcp</code></span></dt>
254<dd><p>
255              Use [do not use] TCP when querying name servers.  The default
256              behavior is to use UDP unless an AXFR or IXFR query is
257              requested, in
258              which case a TCP connection is used.
259            </p></dd>
260<dt><span class="term"><code class="option">+[no]vc</code></span></dt>
261<dd><p>
262              Use [do not use] TCP when querying name servers.  This alternate
263              syntax to <em class="parameter"><code>+[no]tcp</code></em> is
264              provided for backwards
265              compatibility.  The "vc" stands for "virtual circuit".
266            </p></dd>
267<dt><span class="term"><code class="option">+[no]ignore</code></span></dt>
268<dd><p>
269              Ignore truncation in UDP responses instead of retrying with TCP.
270               By
271              default, TCP retries are performed.
272            </p></dd>
273<dt><span class="term"><code class="option">+domain=somename</code></span></dt>
274<dd><p>
275              Set the search list to contain the single domain
276              <em class="parameter"><code>somename</code></em>, as if specified in
277              a
278              <span><strong class="command">domain</strong></span> directive in
279              <code class="filename">/etc/resolv.conf</code>, and enable
280              search list
281              processing as if the <em class="parameter"><code>+search</code></em>
282              option were given.
283            </p></dd>
284<dt><span class="term"><code class="option">+[no]search</code></span></dt>
285<dd><p>
286              Use [do not use] the search list defined by the searchlist or
287              domain
288              directive in <code class="filename">resolv.conf</code> (if
289              any).
290              The search list is not used by default.
291            </p></dd>
292<dt><span class="term"><code class="option">+[no]showsearch</code></span></dt>
293<dd><p>
294              Perform [do not perform] a search showing intermediate
295	      results.
296            </p></dd>
297<dt><span class="term"><code class="option">+[no]defname</code></span></dt>
298<dd><p>
299              Deprecated, treated as a synonym for <em class="parameter"><code>+[no]search</code></em>
300            </p></dd>
301<dt><span class="term"><code class="option">+[no]aaonly</code></span></dt>
302<dd><p>
303              Sets the "aa" flag in the query.
304            </p></dd>
305<dt><span class="term"><code class="option">+[no]aaflag</code></span></dt>
306<dd><p>
307              A synonym for <em class="parameter"><code>+[no]aaonly</code></em>.
308            </p></dd>
309<dt><span class="term"><code class="option">+[no]adflag</code></span></dt>
310<dd><p>
311	      Set [do not set] the AD (authentic data) bit in the
312	      query.  This requests the server to return whether
313	      all of the answer and authority sections have all
314	      been validated as secure according to the security
315	      policy of the server.  AD=1 indicates that all records
316	      have been validated as secure and the answer is not
317	      from a OPT-OUT range.  AD=0 indicate that some part
318	      of the answer was insecure or not validated.
319	    </p></dd>
320<dt><span class="term"><code class="option">+[no]cdflag</code></span></dt>
321<dd><p>
322              Set [do not set] the CD (checking disabled) bit in the query.
323              This
324              requests the server to not perform DNSSEC validation of
325              responses.
326            </p></dd>
327<dt><span class="term"><code class="option">+[no]cl</code></span></dt>
328<dd><p>
329              Display [do not display] the CLASS when printing the record.
330            </p></dd>
331<dt><span class="term"><code class="option">+[no]ttlid</code></span></dt>
332<dd><p>
333              Display [do not display] the TTL when printing the record.
334            </p></dd>
335<dt><span class="term"><code class="option">+[no]recurse</code></span></dt>
336<dd><p>
337              Toggle the setting of the RD (recursion desired) bit in the
338              query.
339              This bit is set by default, which means <span><strong class="command">dig</strong></span>
340              normally sends recursive queries.  Recursion is automatically
341              disabled
342              when the <em class="parameter"><code>+nssearch</code></em> or
343              <em class="parameter"><code>+trace</code></em> query options are
344              used.
345            </p></dd>
346<dt><span class="term"><code class="option">+[no]nssearch</code></span></dt>
347<dd><p>
348              When this option is set, <span><strong class="command">dig</strong></span>
349              attempts to find the
350              authoritative name servers for the zone containing the name
351              being
352              looked up and display the SOA record that each name server has
353              for the
354              zone.
355            </p></dd>
356<dt><span class="term"><code class="option">+[no]trace</code></span></dt>
357<dd><p>
358              Toggle tracing of the delegation path from the root name servers
359              for
360              the name being looked up.  Tracing is disabled by default.  When
361              tracing is enabled, <span><strong class="command">dig</strong></span> makes
362              iterative queries to
363              resolve the name being looked up.  It will follow referrals from
364              the
365              root servers, showing the answer from each server that was used
366              to
367              resolve the lookup.
368            </p></dd>
369<dt><span class="term"><code class="option">+[no]cmd</code></span></dt>
370<dd><p>
371              Toggles the printing of the initial comment in the output
372              identifying
373              the version of <span><strong class="command">dig</strong></span> and the query
374              options that have
375              been applied.  This comment is printed by default.
376            </p></dd>
377<dt><span class="term"><code class="option">+[no]short</code></span></dt>
378<dd><p>
379              Provide a terse answer.  The default is to print the answer in a
380              verbose form.
381            </p></dd>
382<dt><span class="term"><code class="option">+[no]identify</code></span></dt>
383<dd><p>
384              Show [or do not show] the IP address and port number that
385              supplied the
386              answer when the <em class="parameter"><code>+short</code></em> option
387              is enabled.  If
388              short form answers are requested, the default is not to show the
389              source address and port number of the server that provided the
390              answer.
391            </p></dd>
392<dt><span class="term"><code class="option">+[no]comments</code></span></dt>
393<dd><p>
394              Toggle the display of comment lines in the output.  The default
395              is to
396              print comments.
397            </p></dd>
398<dt><span class="term"><code class="option">+[no]stats</code></span></dt>
399<dd><p>
400              This query option toggles the printing of statistics: when the
401              query
402              was made, the size of the reply and so on.  The default
403              behavior is
404              to print the query statistics.
405            </p></dd>
406<dt><span class="term"><code class="option">+[no]qr</code></span></dt>
407<dd><p>
408              Print [do not print] the query as it is sent.
409              By default, the query is not printed.
410            </p></dd>
411<dt><span class="term"><code class="option">+[no]question</code></span></dt>
412<dd><p>
413              Print [do not print] the question section of a query when an
414              answer is
415              returned.  The default is to print the question section as a
416              comment.
417            </p></dd>
418<dt><span class="term"><code class="option">+[no]answer</code></span></dt>
419<dd><p>
420              Display [do not display] the answer section of a reply.  The
421              default
422              is to display it.
423            </p></dd>
424<dt><span class="term"><code class="option">+[no]authority</code></span></dt>
425<dd><p>
426              Display [do not display] the authority section of a reply.  The
427              default is to display it.
428            </p></dd>
429<dt><span class="term"><code class="option">+[no]additional</code></span></dt>
430<dd><p>
431              Display [do not display] the additional section of a reply.
432              The default is to display it.
433            </p></dd>
434<dt><span class="term"><code class="option">+[no]all</code></span></dt>
435<dd><p>
436              Set or clear all display flags.
437            </p></dd>
438<dt><span class="term"><code class="option">+time=T</code></span></dt>
439<dd><p>
440
441              Sets the timeout for a query to
442              <em class="parameter"><code>T</code></em> seconds.  The default
443	      timeout is 5 seconds.
444              An attempt to set <em class="parameter"><code>T</code></em> to less
445              than 1 will result
446              in a query timeout of 1 second being applied.
447            </p></dd>
448<dt><span class="term"><code class="option">+tries=T</code></span></dt>
449<dd><p>
450              Sets the number of times to try UDP queries to server to
451              <em class="parameter"><code>T</code></em> instead of the default, 3.
452              If
453              <em class="parameter"><code>T</code></em> is less than or equal to
454              zero, the number of
455              tries is silently rounded up to 1.
456            </p></dd>
457<dt><span class="term"><code class="option">+retry=T</code></span></dt>
458<dd><p>
459              Sets the number of times to retry UDP queries to server to
460              <em class="parameter"><code>T</code></em> instead of the default, 2.
461              Unlike
462              <em class="parameter"><code>+tries</code></em>, this does not include
463              the initial
464              query.
465            </p></dd>
466<dt><span class="term"><code class="option">+ndots=D</code></span></dt>
467<dd><p>
468              Set the number of dots that have to appear in
469              <em class="parameter"><code>name</code></em> to <em class="parameter"><code>D</code></em> for it to be
470              considered absolute.  The default value is that defined using
471              the
472              ndots statement in <code class="filename">/etc/resolv.conf</code>, or 1 if no
473              ndots statement is present.  Names with fewer dots are
474              interpreted as
475              relative names and will be searched for in the domains listed in
476              the
477              <code class="option">search</code> or <code class="option">domain</code> directive in
478              <code class="filename">/etc/resolv.conf</code>.
479            </p></dd>
480<dt><span class="term"><code class="option">+bufsize=B</code></span></dt>
481<dd><p>
482              Set the UDP message buffer size advertised using EDNS0 to
483              <em class="parameter"><code>B</code></em> bytes.  The maximum and minimum sizes
484	      of this buffer are 65535 and 0 respectively.  Values outside
485	      this range are rounded up or down appropriately.  
486	      Values other than zero will cause a EDNS query to be sent.
487            </p></dd>
488<dt><span class="term"><code class="option">+edns=#</code></span></dt>
489<dd><p>
490	       Specify the EDNS version to query with.  Valid values
491	       are 0 to 255.  Setting the EDNS version will cause a
492	       EDNS query to be sent.  <code class="option">+noedns</code> clears the
493	       remembered EDNS version.
494	    </p></dd>
495<dt><span class="term"><code class="option">+[no]multiline</code></span></dt>
496<dd><p>
497              Print records like the SOA records in a verbose multi-line
498              format with human-readable comments.  The default is to print
499              each record on a single line, to facilitate machine parsing
500              of the <span><strong class="command">dig</strong></span> output.
501            </p></dd>
502<dt><span class="term"><code class="option">+[no]onesoa</code></span></dt>
503<dd><p>
504	      Print only one (starting) SOA record when performing
505	      an AXFR. The default is to print both the starting and
506	      ending SOA records.
507	    </p></dd>
508<dt><span class="term"><code class="option">+[no]fail</code></span></dt>
509<dd><p>
510              Do not try the next server if you receive a SERVFAIL.  The
511              default is
512              to not try the next server which is the reverse of normal stub
513              resolver
514              behavior.
515            </p></dd>
516<dt><span class="term"><code class="option">+[no]besteffort</code></span></dt>
517<dd><p>
518              Attempt to display the contents of messages which are malformed.
519              The default is to not display malformed answers.
520            </p></dd>
521<dt><span class="term"><code class="option">+[no]dnssec</code></span></dt>
522<dd><p>
523              Requests DNSSEC records be sent by setting the DNSSEC OK bit
524              (DO)
525              in the OPT record in the additional section of the query.
526            </p></dd>
527<dt><span class="term"><code class="option">+[no]sigchase</code></span></dt>
528<dd><p>
529              Chase DNSSEC signature chains.  Requires dig be compiled with
530              -DDIG_SIGCHASE.
531            </p></dd>
532<dt><span class="term"><code class="option">+trusted-key=####</code></span></dt>
533<dd>
534<p>
535              Specifies a file containing trusted keys to be used with
536	      <code class="option">+sigchase</code>.  Each DNSKEY record must be
537	      on its own line.
538            </p>
539<p>
540	      If not specified, <span><strong class="command">dig</strong></span> will look for
541	      <code class="filename">/etc/trusted-key.key</code> then
542	      <code class="filename">trusted-key.key</code> in the current directory.
543	    </p>
544<p>
545              Requires dig be compiled with -DDIG_SIGCHASE.
546	    </p>
547</dd>
548<dt><span class="term"><code class="option">+[no]topdown</code></span></dt>
549<dd><p>
550              When chasing DNSSEC signature chains perform a top-down
551              validation.
552              Requires dig be compiled with -DDIG_SIGCHASE.
553            </p></dd>
554<dt><span class="term"><code class="option">+[no]nsid</code></span></dt>
555<dd><p>
556              Include an EDNS name server ID request when sending a query.
557            </p></dd>
558</dl></div>
559<p>
560
561    </p>
562</div>
563<div class="refsect1" lang="en">
564<a name="id2545186"></a><h2>MULTIPLE QUERIES</h2>
565<p>
566      The BIND 9 implementation of <span><strong class="command">dig </strong></span>
567      supports
568      specifying multiple queries on the command line (in addition to
569      supporting the <code class="option">-f</code> batch file option).  Each of those
570      queries can be supplied with its own set of flags, options and query
571      options.
572    </p>
573<p>
574      In this case, each <em class="parameter"><code>query</code></em> argument
575      represent an
576      individual query in the command-line syntax described above.  Each
577      consists of any of the standard options and flags, the name to be
578      looked up, an optional query type and class and any query options that
579      should be applied to that query.
580    </p>
581<p>
582      A global set of query options, which should be applied to all queries,
583      can also be supplied.  These global query options must precede the
584      first tuple of name, class, type, options, flags, and query options
585      supplied on the command line.  Any global query options (except
586      the <code class="option">+[no]cmd</code> option) can be
587      overridden by a query-specific set of query options.  For example:
588      </p>
589<pre class="programlisting">
590dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
591</pre>
592<p>
593      shows how <span><strong class="command">dig</strong></span> could be used from the
594      command line
595      to make three lookups: an ANY query for <code class="literal">www.isc.org</code>, a
596      reverse lookup of 127.0.0.1 and a query for the NS records of
597      <code class="literal">isc.org</code>.
598
599      A global query option of <em class="parameter"><code>+qr</code></em> is
600      applied, so
601      that <span><strong class="command">dig</strong></span> shows the initial query it made
602      for each
603      lookup.  The final query has a local query option of
604      <em class="parameter"><code>+noqr</code></em> which means that <span><strong class="command">dig</strong></span>
605      will not print the initial query when it looks up the NS records for
606      <code class="literal">isc.org</code>.
607    </p>
608</div>
609<div class="refsect1" lang="en">
610<a name="id2545248"></a><h2>IDN SUPPORT</h2>
611<p>
612      If <span><strong class="command">dig</strong></span> has been built with IDN (internationalized
613      domain name) support, it can accept and display non-ASCII domain names.
614      <span><strong class="command">dig</strong></span> appropriately converts character encoding of
615      domain name before sending a request to DNS server or displaying a
616      reply from the server.
617      If you'd like to turn off the IDN support for some reason, defines
618      the <code class="envar">IDN_DISABLE</code> environment variable.
619      The IDN support is disabled if the variable is set when 
620      <span><strong class="command">dig</strong></span> runs.
621    </p>
622</div>
623<div class="refsect1" lang="en">
624<a name="id2545338"></a><h2>FILES</h2>
625<p><code class="filename">/etc/resolv.conf</code>
626    </p>
627<p><code class="filename">${HOME}/.digrc</code>
628    </p>
629</div>
630<div class="refsect1" lang="en">
631<a name="id2545355"></a><h2>SEE ALSO</h2>
632<p><span class="citerefentry"><span class="refentrytitle">host</span>(1)</span>,
633      <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
634      <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
635      <em class="citetitle">RFC1035</em>.
636    </p>
637</div>
638<div class="refsect1" lang="en">
639<a name="id2545393"></a><h2>BUGS</h2>
640<p>
641      There are probably too many query options.
642    </p>
643</div>
644</div></body>
645</html>