contrib/bind9/bin/dig/dig.html

   1 <!--
   2  - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC")
   3  - Copyright (C) 2000-2003 Internet Software Consortium.
   4  -
   5  - Permission to use, copy, modify, and 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: dig.html,v 1.13.18.28 2007/05/16 06:11:27 marka 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 </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">-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="id2543508"></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, will perform an
  66       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 or
  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="id2543577"></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="id2543668"></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       If a non-standard port number is to be queried, the
 156       <code class="option">-p</code> option is used.  <em class="parameter"><code>port#</code></em> is
 157       the port number that <span><strong class="command">dig</strong></span> will send its
 158       queries
 159       instead of the standard DNS port number 53.  This option would be used
 160       to test a name server that has been configured to listen for queries
 161       on a non-standard port number.
 162     </p>
 163 <p>
 164       The <code class="option">-4</code> option forces <span><strong class="command">dig</strong></span>
 165       to only
 166       use IPv4 query transport.  The <code class="option">-6</code> option forces
 167       <span><strong class="command">dig</strong></span> to only use IPv6 query transport.
 168     </p>
 169 <p>
 170       The <code class="option">-t</code> option sets the query type to
 171       <em class="parameter"><code>type</code></em>.  It can be any valid query type
 172       which is
 173       supported in BIND 9.  The default query type is "A", unless the
 174       <code class="option">-x</code> option is supplied to indicate a reverse lookup.
 175       A zone transfer can be requested by specifying a type of AXFR.  When
 176       an incremental zone transfer (IXFR) is required,
 177       <em class="parameter"><code>type</code></em> is set to <code class="literal">ixfr=N</code>.
 178       The incremental zone transfer will contain the changes made to the zone
 179       since the serial number in the zone's SOA record was
 180       <em class="parameter"><code>N</code></em>.
 181     </p>
 182 <p>
 183       The <code class="option">-q</code> option sets the query name to
 184       <em class="parameter"><code>name</code></em>.  This useful do distinguish the
 185       <em class="parameter"><code>name</code></em> from other arguments.
 186     </p>
 187 <p>
 188       Reverse lookups &#8212; mapping addresses to names &#8212; are simplified by the
 189       <code class="option">-x</code> option.  <em class="parameter"><code>addr</code></em> is
 190       an IPv4
 191       address in dotted-decimal notation, or a colon-delimited IPv6 address.
 192       When this option is used, there is no need to provide the
 193       <em class="parameter"><code>name</code></em>, <em class="parameter"><code>class</code></em> and
 194       <em class="parameter"><code>type</code></em> arguments.  <span><strong class="command">dig</strong></span>
 195       automatically performs a lookup for a name like
 196       <code class="literal">11.12.13.10.in-addr.arpa</code> and sets the
 197       query type and
 198       class to PTR and IN respectively.  By default, IPv6 addresses are
 199       looked up using nibble format under the IP6.ARPA domain.
 200       To use the older RFC1886 method using the IP6.INT domain
 201       specify the <code class="option">-i</code> option.  Bit string labels (RFC2874)
 202       are now experimental and are not attempted.
 203     </p>
 204 <p>
 205       To sign the DNS queries sent by <span><strong class="command">dig</strong></span> and
 206       their
 207       responses using transaction signatures (TSIG), specify a TSIG key file
 208       using the <code class="option">-k</code> option.  You can also specify the TSIG
 209       key itself on the command line using the <code class="option">-y</code> option;
 210       <em class="parameter"><code>hmac</code></em> is the type of the TSIG, default HMAC-MD5,
 211       <em class="parameter"><code>name</code></em> is the name of the TSIG key and
 212       <em class="parameter"><code>key</code></em> is the actual key.  The key is a
 213       base-64
 214       encoded string, typically generated by
 215       <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
 216
 217       Caution should be taken when using the <code class="option">-y</code> option on
 218       multi-user systems as the key can be visible in the output from
 219       <span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
 220       or in the shell's history file.  When
 221       using TSIG authentication with <span><strong class="command">dig</strong></span>, the name
 222       server that is queried needs to know the key and algorithm that is
 223       being used.  In BIND, this is done by providing appropriate
 224       <span><strong class="command">key</strong></span> and <span><strong class="command">server</strong></span> statements in
 225       <code class="filename">named.conf</code>.
 226     </p>
 227 </div>
 228 <div class="refsect1" lang="en">
 229 <a name="id2543939"></a><h2>QUERY OPTIONS</h2>
 230 <p><span><strong class="command">dig</strong></span>
 231       provides a number of query options which affect
 232       the way in which lookups are made and the results displayed.  Some of
 233       these set or reset flag bits in the query header, some determine which
 234       sections of the answer get printed, and others determine the timeout
 235       and retry strategies.
 236     </p>
 237 <p>
 238       Each query option is identified by a keyword preceded by a plus sign
 239       (<code class="literal">+</code>).  Some keywords set or reset an
 240       option.  These may be preceded
 241       by the string <code class="literal">no</code> to negate the meaning of
 242       that keyword.  Other
 243       keywords assign values to options like the timeout interval.  They
 244       have the form <code class="option">+keyword=value</code>.
 245       The query options are:
 246
 247       </p>
 248 <div class="variablelist"><dl>
 249 <dt><span class="term"><code class="option">+[no]tcp</code></span></dt>
 250 <dd><p>
 251               Use [do not use] TCP when querying name servers.  The default
 252               behavior is to use UDP unless an AXFR or IXFR query is
 253               requested, in
 254               which case a TCP connection is used.
 255             </p></dd>
 256 <dt><span class="term"><code class="option">+[no]vc</code></span></dt>
 257 <dd><p>
 258               Use [do not use] TCP when querying name servers.  This alternate
 259               syntax to <em class="parameter"><code>+[no]tcp</code></em> is
 260               provided for backwards
 261               compatibility.  The "vc" stands for "virtual circuit".
 262             </p></dd>
 263 <dt><span class="term"><code class="option">+[no]ignore</code></span></dt>
 264 <dd><p>
 265               Ignore truncation in UDP responses instead of retrying with TCP.
 266                By
 267               default, TCP retries are performed.
 268             </p></dd>
 269 <dt><span class="term"><code class="option">+domain=somename</code></span></dt>
 270 <dd><p>
 271               Set the search list to contain the single domain
 272               <em class="parameter"><code>somename</code></em>, as if specified in
 273               a
 274               <span><strong class="command">domain</strong></span> directive in
 275               <code class="filename">/etc/resolv.conf</code>, and enable
 276               search list
 277               processing as if the <em class="parameter"><code>+search</code></em>
 278               option were given.
 279             </p></dd>
 280 <dt><span class="term"><code class="option">+[no]search</code></span></dt>
 281 <dd><p>
 282               Use [do not use] the search list defined by the searchlist or
 283               domain
 284               directive in <code class="filename">resolv.conf</code> (if
 285               any).
 286               The search list is not used by default.
 287             </p></dd>
 288 <dt><span class="term"><code class="option">+[no]showsearch</code></span></dt>
 289 <dd><p>
 290               Perform [do not perform] a search showing intermediate
 291               results.
 292             </p></dd>
 293 <dt><span class="term"><code class="option">+[no]defname</code></span></dt>
 294 <dd><p>
 295               Deprecated, treated as a synonym for <em class="parameter"><code>+[no]search</code></em>
 296             </p></dd>
 297 <dt><span class="term"><code class="option">+[no]aaonly</code></span></dt>
 298 <dd><p>
 299               Sets the "aa" flag in the query.
 300             </p></dd>
 301 <dt><span class="term"><code class="option">+[no]aaflag</code></span></dt>
 302 <dd><p>
 303               A synonym for <em class="parameter"><code>+[no]aaonly</code></em>.
 304             </p></dd>
 305 <dt><span class="term"><code class="option">+[no]adflag</code></span></dt>
 306 <dd><p>
 307               Set [do not set] the AD (authentic data) bit in the query.  The
 308               AD bit
 309               currently has a standard meaning only in responses, not in
 310               queries,
 311               but the ability to set the bit in the query is provided for
 312               completeness.
 313             </p></dd>
 314 <dt><span class="term"><code class="option">+[no]cdflag</code></span></dt>
 315 <dd><p>
 316               Set [do not set] the CD (checking disabled) bit in the query.
 317               This
 318               requests the server to not perform DNSSEC validation of
 319               responses.
 320             </p></dd>
 321 <dt><span class="term"><code class="option">+[no]cl</code></span></dt>
 322 <dd><p>
 323               Display [do not display] the CLASS when printing the record.
 324             </p></dd>
 325 <dt><span class="term"><code class="option">+[no]ttlid</code></span></dt>
 326 <dd><p>
 327               Display [do not display] the TTL when printing the record.
 328             </p></dd>
 329 <dt><span class="term"><code class="option">+[no]recurse</code></span></dt>
 330 <dd><p>
 331               Toggle the setting of the RD (recursion desired) bit in the
 332               query.
 333               This bit is set by default, which means <span><strong class="command">dig</strong></span>
 334               normally sends recursive queries.  Recursion is automatically
 335               disabled
 336               when the <em class="parameter"><code>+nssearch</code></em> or
 337               <em class="parameter"><code>+trace</code></em> query options are
 338               used.
 339             </p></dd>
 340 <dt><span class="term"><code class="option">+[no]nssearch</code></span></dt>
 341 <dd><p>
 342               When this option is set, <span><strong class="command">dig</strong></span>
 343               attempts to find the
 344               authoritative name servers for the zone containing the name
 345               being
 346               looked up and display the SOA record that each name server has
 347               for the
 348               zone.
 349             </p></dd>
 350 <dt><span class="term"><code class="option">+[no]trace</code></span></dt>
 351 <dd><p>
 352               Toggle tracing of the delegation path from the root name servers
 353               for
 354               the name being looked up.  Tracing is disabled by default.  When
 355               tracing is enabled, <span><strong class="command">dig</strong></span> makes
 356               iterative queries to
 357               resolve the name being looked up.  It will follow referrals from
 358               the
 359               root servers, showing the answer from each server that was used
 360               to
 361               resolve the lookup.
 362             </p></dd>
 363 <dt><span class="term"><code class="option">+[no]cmd</code></span></dt>
 364 <dd><p>
 365               Toggles the printing of the initial comment in the output
 366               identifying
 367               the version of <span><strong class="command">dig</strong></span> and the query
 368               options that have
 369               been applied.  This comment is printed by default.
 370             </p></dd>
 371 <dt><span class="term"><code class="option">+[no]short</code></span></dt>
 372 <dd><p>
 373               Provide a terse answer.  The default is to print the answer in a
 374               verbose form.
 375             </p></dd>
 376 <dt><span class="term"><code class="option">+[no]identify</code></span></dt>
 377 <dd><p>
 378               Show [or do not show] the IP address and port number that
 379               supplied the
 380               answer when the <em class="parameter"><code>+short</code></em> option
 381               is enabled.  If
 382               short form answers are requested, the default is not to show the
 383               source address and port number of the server that provided the
 384               answer.
 385             </p></dd>
 386 <dt><span class="term"><code class="option">+[no]comments</code></span></dt>
 387 <dd><p>
 388               Toggle the display of comment lines in the output.  The default
 389               is to
 390               print comments.
 391             </p></dd>
 392 <dt><span class="term"><code class="option">+[no]stats</code></span></dt>
 393 <dd><p>
 394               This query option toggles the printing of statistics: when the
 395               query
 396               was made, the size of the reply and so on.  The default
 397               behavior is
 398               to print the query statistics.
 399             </p></dd>
 400 <dt><span class="term"><code class="option">+[no]qr</code></span></dt>
 401 <dd><p>
 402               Print [do not print] the query as it is sent.
 403               By default, the query is not printed.
 404             </p></dd>
 405 <dt><span class="term"><code class="option">+[no]question</code></span></dt>
 406 <dd><p>
 407               Print [do not print] the question section of a query when an
 408               answer is
 409               returned.  The default is to print the question section as a
 410               comment.
 411             </p></dd>
 412 <dt><span class="term"><code class="option">+[no]answer</code></span></dt>
 413 <dd><p>
 414               Display [do not display] the answer section of a reply.  The
 415               default
 416               is to display it.
 417             </p></dd>
 418 <dt><span class="term"><code class="option">+[no]authority</code></span></dt>
 419 <dd><p>
 420               Display [do not display] the authority section of a reply.  The
 421               default is to display it.
 422             </p></dd>
 423 <dt><span class="term"><code class="option">+[no]additional</code></span></dt>
 424 <dd><p>
 425               Display [do not display] the additional section of a reply.
 426               The default is to display it.
 427             </p></dd>
 428 <dt><span class="term"><code class="option">+[no]all</code></span></dt>
 429 <dd><p>
 430               Set or clear all display flags.
 431             </p></dd>
 432 <dt><span class="term"><code class="option">+time=T</code></span></dt>
 433 <dd><p>
 434
 435               Sets the timeout for a query to
 436               <em class="parameter"><code>T</code></em> seconds.  The default
 437               timeout is 5 seconds.
 438               An attempt to set <em class="parameter"><code>T</code></em> to less
 439               than 1 will result
 440               in a query timeout of 1 second being applied.
 441             </p></dd>
 442 <dt><span class="term"><code class="option">+tries=T</code></span></dt>
 443 <dd><p>
 444               Sets the number of times to try UDP queries to server to
 445               <em class="parameter"><code>T</code></em> instead of the default, 3.
 446               If
 447               <em class="parameter"><code>T</code></em> is less than or equal to
 448               zero, the number of
 449               tries is silently rounded up to 1.
 450             </p></dd>
 451 <dt><span class="term"><code class="option">+retry=T</code></span></dt>
 452 <dd><p>
 453               Sets the number of times to retry UDP queries to server to
 454               <em class="parameter"><code>T</code></em> instead of the default, 2.
 455               Unlike
 456               <em class="parameter"><code>+tries</code></em>, this does not include
 457               the initial
 458               query.
 459             </p></dd>
 460 <dt><span class="term"><code class="option">+ndots=D</code></span></dt>
 461 <dd><p>
 462               Set the number of dots that have to appear in
 463               <em class="parameter"><code>name</code></em> to <em class="parameter"><code>D</code></em> for it to be
 464               considered absolute.  The default value is that defined using
 465               the
 466               ndots statement in <code class="filename">/etc/resolv.conf</code>, or 1 if no
 467               ndots statement is present.  Names with fewer dots are
 468               interpreted as
 469               relative names and will be searched for in the domains listed in
 470               the
 471               <code class="option">search</code> or <code class="option">domain</code> directive in
 472               <code class="filename">/etc/resolv.conf</code>.
 473             </p></dd>
 474 <dt><span class="term"><code class="option">+bufsize=B</code></span></dt>
 475 <dd><p>
 476               Set the UDP message buffer size advertised using EDNS0 to
 477               <em class="parameter"><code>B</code></em> bytes.  The maximum and minimum sizes
 478               of this buffer are 65535 and 0 respectively.  Values outside
 479               this range are rounded up or down appropriately.
 480               Values other than zero will cause a EDNS query to be sent.
 481             </p></dd>
 482 <dt><span class="term"><code class="option">+edns=#</code></span></dt>
 483 <dd><p>
 484                Specify the EDNS version to query with.  Valid values
 485                are 0 to 255.  Setting the EDNS version will cause a
 486                EDNS query to be sent.  <code class="option">+noedns</code> clears the
 487                remembered EDNS version.
 488             </p></dd>
 489 <dt><span class="term"><code class="option">+[no]multiline</code></span></dt>
 490 <dd><p>
 491               Print records like the SOA records in a verbose multi-line
 492               format with human-readable comments.  The default is to print
 493               each record on a single line, to facilitate machine parsing
 494               of the <span><strong class="command">dig</strong></span> output.
 495             </p></dd>
 496 <dt><span class="term"><code class="option">+[no]fail</code></span></dt>
 497 <dd><p>
 498               Do not try the next server if you receive a SERVFAIL.  The
 499               default is
 500               to not try the next server which is the reverse of normal stub
 501               resolver
 502               behavior.
 503             </p></dd>
 504 <dt><span class="term"><code class="option">+[no]besteffort</code></span></dt>
 505 <dd><p>
 506               Attempt to display the contents of messages which are malformed.
 507               The default is to not display malformed answers.
 508             </p></dd>
 509 <dt><span class="term"><code class="option">+[no]dnssec</code></span></dt>
 510 <dd><p>
 511               Requests DNSSEC records be sent by setting the DNSSEC OK bit
 512               (DO)
 513               in the OPT record in the additional section of the query.
 514             </p></dd>
 515 <dt><span class="term"><code class="option">+[no]sigchase</code></span></dt>
 516 <dd><p>
 517               Chase DNSSEC signature chains.  Requires dig be compiled with
 518               -DDIG_SIGCHASE.
 519             </p></dd>
 520 <dt><span class="term"><code class="option">+trusted-key=####</code></span></dt>
 521 <dd>
 522 <p>
 523               Specifies a file containing trusted keys to be used with
 524               <code class="option">+sigchase</code>.  Each DNSKEY record must be
 525               on its own line.
 526             </p>
 527 <p>
 528               If not specified <span><strong class="command">dig</strong></span> will look for
 529               <code class="filename">/etc/trusted-key.key</code> then
 530               <code class="filename">trusted-key.key</code> in the current directory.
 531             </p>
 532 <p>
 533               Requires dig be compiled with -DDIG_SIGCHASE.
 534             </p>
 535 </dd>
 536 <dt><span class="term"><code class="option">+[no]topdown</code></span></dt>
 537 <dd><p>
 538               When chasing DNSSEC signature chains perform a top-down
 539               validation.
 540               Requires dig be compiled with -DDIG_SIGCHASE.
 541             </p></dd>
 542 </dl></div>
 543 <p>
 544
 545     </p>
 546 </div>
 547 <div class="refsect1" lang="en">
 548 <a name="id2545128"></a><h2>MULTIPLE QUERIES</h2>
 549 <p>
 550       The BIND 9 implementation of <span><strong class="command">dig </strong></span>
 551       supports
 552       specifying multiple queries on the command line (in addition to
 553       supporting the <code class="option">-f</code> batch file option).  Each of those
 554       queries can be supplied with its own set of flags, options and query
 555       options.
 556     </p>
 557 <p>
 558       In this case, each <em class="parameter"><code>query</code></em> argument
 559       represent an
 560       individual query in the command-line syntax described above.  Each
 561       consists of any of the standard options and flags, the name to be
 562       looked up, an optional query type and class and any query options that
 563       should be applied to that query.
 564     </p>
 565 <p>
 566       A global set of query options, which should be applied to all queries,
 567       can also be supplied.  These global query options must precede the
 568       first tuple of name, class, type, options, flags, and query options
 569       supplied on the command line.  Any global query options (except
 570       the <code class="option">+[no]cmd</code> option) can be
 571       overridden by a query-specific set of query options.  For example:
 572       </p>
 573 <pre class="programlisting">
 574 dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
 575 </pre>
 576 <p>
 577       shows how <span><strong class="command">dig</strong></span> could be used from the
 578       command line
 579       to make three lookups: an ANY query for <code class="literal">www.isc.org</code>, a
 580       reverse lookup of 127.0.0.1 and a query for the NS records of
 581       <code class="literal">isc.org</code>.
 582
 583       A global query option of <em class="parameter"><code>+qr</code></em> is
 584       applied, so
 585       that <span><strong class="command">dig</strong></span> shows the initial query it made
 586       for each
 587       lookup.  The final query has a local query option of
 588       <em class="parameter"><code>+noqr</code></em> which means that <span><strong class="command">dig</strong></span>
 589       will not print the initial query when it looks up the NS records for
 590       <code class="literal">isc.org</code>.
 591     </p>
 592 </div>
 593 <div class="refsect1" lang="en">
 594 <a name="id2545258"></a><h2>IDN SUPPORT</h2>
 595 <p>
 596       If <span><strong class="command">dig</strong></span> has been built with IDN (internationalized
 597       domain name) support, it can accept and display non-ASCII domain names.
 598       <span><strong class="command">dig</strong></span> appropriately converts character encoding of
 599       domain name before sending a request to DNS server or displaying a
 600       reply from the server.
 601       If you'd like to turn off the IDN support for some reason, defines
 602       the <code class="envar">IDN_DISABLE</code> environment variable.
 603       The IDN support is disabled if the variable is set when
 604       <span><strong class="command">dig</strong></span> runs.
 605     </p>
 606 </div>
 607 <div class="refsect1" lang="en">
 608 <a name="id2545281"></a><h2>FILES</h2>
 609 <p><code class="filename">/etc/resolv.conf</code>
 610     </p>
 611 <p><code class="filename">${HOME}/.digrc</code>
 612     </p>
 613 </div>
 614 <div class="refsect1" lang="en">
 615 <a name="id2545298"></a><h2>SEE ALSO</h2>
 616 <p><span class="citerefentry"><span class="refentrytitle">host</span>(1)</span>,
 617       <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
 618       <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
 619       <em class="citetitle">RFC1035</em>.
 620     </p>
 621 </div>
 622 <div class="refsect1" lang="en">
 623 <a name="id2545335"></a><h2>BUGS</h2>
 624 <p>
 625       There are probably too many query options.
 626     </p>
 627 </div>
 628 </div></body>
 629 </html>