external/bsd/bind/dist/doc/arm/man.dig.html

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