man.dig.html revision 665a24faf6b3711e4012ac02ae5f0981c093ac1e
448N/A<!--
448N/A - Copyright (C) 2004-2014 Internet Systems Consortium, Inc. ("ISC")
448N/A - Copyright (C) 2000-2003 Internet Software Consortium.
953N/A -
814N/A - Permission to use, copy, modify, and/or distribute this software for any
852N/A - purpose with or without fee is hereby granted, provided that the above
448N/A - copyright notice and this permission notice appear in all copies.
448N/A -
448N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
448N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
448N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
448N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
448N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
448N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
448N/A - PERFORMANCE OF THIS SOFTWARE.
448N/A-->
448N/A<!-- $Id$ -->
448N/A<html>
448N/A<head>
448N/A<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
448N/A<title>dig</title>
448N/A<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
448N/A<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
448N/A<link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
448N/A<link rel="prev" href="Bv9ARM.ch10.html" title="Manual pages">
502N/A<link rel="next" href="man.host.html" title="host">
502N/A</head>
502N/A<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
448N/A<div class="navheader">
448N/A<table width="100%" summary="Navigation header">
448N/A<tr><th colspan="3" align="center">dig</th></tr>
448N/A<tr>
448N/A<td width="20%" align="left">
448N/A<a accesskey="p" href="Bv9ARM.ch10.html">Prev</a>�</td>
448N/A<th width="60%" align="center">Manual pages</th>
448N/A<td width="20%" align="right">�<a accesskey="n" href="man.host.html">Next</a>
448N/A</td>
448N/A</tr>
448N/A</table>
448N/A<hr>
448N/A</div>
448N/A<div class="refentry" lang="en">
448N/A<a name="man.dig"></a><div class="titlepage"></div>
448N/A<div class="refnamediv">
448N/A<h2>Name</h2>
448N/A<p>dig &#8212; DNS lookup utility</p>
448N/A</div>
448N/A<div class="refsynopsisdiv">
448N/A<h2>Synopsis</h2>
448N/A<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>
448N/A<div class="cmdsynopsis"><p><code class="command">dig</code> [<code class="option">-h</code>]</p></div>
448N/A<div class="cmdsynopsis"><p><code class="command">dig</code> [global-queryopt...] [query...]</p></div>
448N/A</div>
526N/A<div class="refsect1" lang="en">
448N/A<a name="id2613296"></a><h2>DESCRIPTION</h2>
526N/A<p><span><strong class="command">dig</strong></span>
526N/A (domain information groper) is a flexible tool
526N/A for interrogating DNS name servers. It performs DNS lookups and
526N/A displays the answers that are returned from the name server(s) that
526N/A were queried. Most DNS administrators use <span><strong class="command">dig</strong></span> to
526N/A troubleshoot DNS problems because of its flexibility, ease of use and
526N/A clarity of output. Other lookup tools tend to have less functionality
526N/A than <span><strong class="command">dig</strong></span>.
526N/A </p>
448N/A<p>
526N/A Although <span><strong class="command">dig</strong></span> is normally used with
526N/A command-line
526N/A arguments, it also has a batch mode of operation for reading lookup
526N/A requests from a file. A brief summary of its command-line arguments
526N/A and options is printed when the <code class="option">-h</code> option is given.
526N/A Unlike earlier versions, the BIND 9 implementation of
526N/A <span><strong class="command">dig</strong></span> allows multiple lookups to be issued
526N/A from the
933N/A command line.
448N/A </p>
448N/A<p>
448N/A Unless it is told to query a specific name server,
448N/A <span><strong class="command">dig</strong></span> will try each of the servers listed in
926N/A <code class="filename">/etc/resolv.conf</code>. If no usable server addresses
448N/A are found, <span><strong class="command">dig</strong></span> will send the query to the local
448N/A host.
448N/A </p>
448N/A<p>
448N/A When no command line arguments or options are given,
448N/A <span><strong class="command">dig</strong></span> will perform an NS query for "." (the root).
448N/A </p>
448N/A<p>
448N/A It is possible to set per-user defaults for <span><strong class="command">dig</strong></span> via
448N/A <code class="filename">${HOME}/.digrc</code>. This file is read and
448N/A any options in it
526N/A are applied before the command line arguments.
526N/A </p>
526N/A<p>
526N/A The IN and CH class names overlap with the IN and CH top level
526N/A domain names. Either use the <code class="option">-t</code> and
526N/A <code class="option">-c</code> options to specify the type and class,
933N/A use the <code class="option">-q</code> the specify the domain name, or
1027N/A use "IN." and "CH." when looking up these top level domains.
1027N/A </p>
1027N/A</div>
1027N/A<div class="refsect1" lang="en">
1027N/A<a name="id2613398"></a><h2>SIMPLE USAGE</h2>
1027N/A<p>
1027N/A A typical invocation of <span><strong class="command">dig</strong></span> looks like:
1027N/A </p>
1027N/A<pre class="programlisting"> dig @server name type </pre>
1027N/A<p>
1027N/A where:
1032N/A
926N/A </p>
926N/A<div class="variablelist"><dl>
926N/A<dt><span class="term"><code class="constant">server</code></span></dt>
448N/A<dd>
448N/A<p>
448N/A is the name or IP address of the name server to query. This
448N/A can be an IPv4 address in dotted-decimal notation or an IPv6
448N/A address in colon-delimited notation. When the supplied
448N/A <em class="parameter"><code>server</code></em> argument is a hostname,
448N/A <span><strong class="command">dig</strong></span> resolves that name before querying
448N/A that name server.
448N/A </p>
448N/A<p>
448N/A If no <em class="parameter"><code>server</code></em> argument is
448N/A provided, <span><strong class="command">dig</strong></span> consults
448N/A <code class="filename">/etc/resolv.conf</code>; if an
448N/A address is found there, it queries the name server at
448N/A that address. If either of the <code class="option">-4</code> or
448N/A <code class="option">-6</code> options are in use, then
448N/A only addresses for the corresponding transport
448N/A will be tried. If no usable addresses are found,
448N/A <span><strong class="command">dig</strong></span> will send the query to the
481N/A local host. The reply from the name server that
448N/A responds is displayed.
448N/A </p>
448N/A</dd>
448N/A<dt><span class="term"><code class="constant">name</code></span></dt>
448N/A<dd><p>
448N/A is the name of the resource record that is to be looked up.
448N/A </p></dd>
448N/A<dt><span class="term"><code class="constant">type</code></span></dt>
448N/A<dd><p>
448N/A indicates what type of query is required &#8212;
448N/A ANY, A, MX, SIG, etc.
448N/A <em class="parameter"><code>type</code></em> can be any valid query
448N/A type. If no
448N/A <em class="parameter"><code>type</code></em> argument is supplied,
448N/A <span><strong class="command">dig</strong></span> will perform a lookup for an
448N/A A record.
448N/A </p></dd>
448N/A</dl></div>
448N/A<p>
448N/A </p>
448N/A</div>
448N/A<div class="refsect1" lang="en">
448N/A<a name="id2613592"></a><h2>OPTIONS</h2>
564N/A<p>
564N/A The <code class="option">-b</code> option sets the source IP address of the query
564N/A to <em class="parameter"><code>address</code></em>. This must be a valid
564N/A address on
564N/A one of the host's network interfaces or "0.0.0.0" or "::". An optional
564N/A port
526N/A may be specified by appending "#&lt;port&gt;"
526N/A </p>
526N/A<p>
526N/A The default query class (IN for internet) is overridden by the
526N/A <code class="option">-c</code> option. <em class="parameter"><code>class</code></em> is
526N/A any valid
526N/A class, such as HS for Hesiod records or CH for Chaosnet records.
448N/A </p>
448N/A<p>
448N/A The <code class="option">-f</code> option makes <span><strong class="command">dig </strong></span>
448N/A operate
448N/A in batch mode by reading a list of lookup requests to process from the
448N/A file <em class="parameter"><code>filename</code></em>. The file contains a
448N/A number of
448N/A queries, one per line. Each entry in the file should be organized in
448N/A the same way they would be presented as queries to
526N/A <span><strong class="command">dig</strong></span> using the command-line interface.
448N/A </p>
448N/A<p>
448N/A The <code class="option">-m</code> option enables memory usage debugging.
448N/A
448N/A </p>
448N/A<p>
448N/A If a non-standard port number is to be queried, the
448N/A <code class="option">-p</code> option is used. <em class="parameter"><code>port#</code></em> is
448N/A the port number that <span><strong class="command">dig</strong></span> will send its
448N/A queries
448N/A instead of the standard DNS port number 53. This option would be used
448N/A to test a name server that has been configured to listen for queries
448N/A on a non-standard port number.
448N/A </p>
448N/A<p>
448N/A The <code class="option">-4</code> option forces <span><strong class="command">dig</strong></span>
448N/A to only
448N/A use IPv4 query transport. The <code class="option">-6</code> option forces
448N/A <span><strong class="command">dig</strong></span> to only use IPv6 query transport.
448N/A </p>
448N/A<p>
448N/A The <code class="option">-t</code> option sets the query type to
448N/A <em class="parameter"><code>type</code></em>. It can be any valid query type
448N/A which is
448N/A supported in BIND 9. The default query type is "A", unless the
448N/A <code class="option">-x</code> option is supplied to indicate a reverse lookup.
448N/A A zone transfer can be requested by specifying a type of AXFR. When
584N/A an incremental zone transfer (IXFR) is required,
565N/A <em class="parameter"><code>type</code></em> is set to <code class="literal">ixfr=N</code>.
926N/A The incremental zone transfer will contain the changes made to the zone
565N/A since the serial number in the zone's SOA record was
565N/A <em class="parameter"><code>N</code></em>.
941N/A </p>
941N/A<p>
941N/A The <code class="option">-q</code> option sets the query name to
941N/A <em class="parameter"><code>name</code></em>. This is useful to distinguish the
941N/A <em class="parameter"><code>name</code></em> from other arguments.
941N/A </p>
941N/A<p>
941N/A Reverse lookups &#8212; mapping addresses to names &#8212; are simplified by the
941N/A <code class="option">-x</code> option. <em class="parameter"><code>addr</code></em> is
941N/A an IPv4
1009N/A address in dotted-decimal notation, or a colon-delimited IPv6 address.
1009N/A When this option is used, there is no need to provide the
983N/A <em class="parameter"><code>name</code></em>, <em class="parameter"><code>class</code></em> and
941N/A <em class="parameter"><code>type</code></em> arguments. <span><strong class="command">dig</strong></span>
941N/A automatically performs a lookup for a name like
941N/A <code class="literal">11.12.13.10.in-addr.arpa</code> and sets the
941N/A query type and
941N/A class to PTR and IN respectively. By default, IPv6 addresses are
941N/A looked up using nibble format under the IP6.ARPA domain.
941N/A To use the older RFC1886 method using the IP6.INT domain
941N/A specify the <code class="option">-i</code> option. Bit string labels (RFC2874)
941N/A are now experimental and are not attempted.
941N/A </p>
941N/A<p>
941N/A To sign the DNS queries sent by <span><strong class="command">dig</strong></span> and
583N/A their
583N/A responses using transaction signatures (TSIG), specify a TSIG key file
581N/A using the <code class="option">-k</code> option. You can also specify the TSIG
581N/A key itself on the command line using the <code class="option">-y</code> option;
616N/A <em class="parameter"><code>hmac</code></em> is the type of the TSIG, default HMAC-MD5,
565N/A <em class="parameter"><code>name</code></em> is the name of the TSIG key and
565N/A <em class="parameter"><code>key</code></em> is the actual key. The key is a
565N/A base-64
565N/A encoded string, typically generated by
565N/A <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
565N/A
565N/A Caution should be taken when using the <code class="option">-y</code> option on
565N/A multi-user systems as the key can be visible in the output from
565N/A <span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
565N/A or in the shell's history file. When
655N/A using TSIG authentication with <span><strong class="command">dig</strong></span>, the name
565N/A server that is queried needs to know the key and algorithm that is
565N/A being used. In BIND, this is done by providing appropriate
565N/A <span><strong class="command">key</strong></span> and <span><strong class="command">server</strong></span> statements in
565N/A <code class="filename">named.conf</code>.
581N/A </p>
581N/A</div>
581N/A<div class="refsect1" lang="en">
581N/A<a name="id2665954"></a><h2>QUERY OPTIONS</h2>
581N/A<p><span><strong class="command">dig</strong></span>
581N/A provides a number of query options which affect
581N/A the way in which lookups are made and the results displayed. Some of
581N/A these set or reset flag bits in the query header, some determine which
797N/A sections of the answer get printed, and others determine the timeout
975N/A and retry strategies.
817N/A </p>
581N/A<p>
581N/A Each query option is identified by a keyword preceded by a plus sign
581N/A (<code class="literal">+</code>). Some keywords set or reset an
599N/A option. These may be preceded
933N/A by the string <code class="literal">no</code> to negate the meaning of
689N/A that keyword. Other
738N/A keywords assign values to options like the timeout interval. They
1025N/A have the form <code class="option">+keyword=value</code>.
581N/A The query options are:
742N/A
873N/A </p>
934N/A<div class="variablelist"><dl>
539N/A<dt><span class="term"><code class="option">+[no]tcp</code></span></dt>
539N/A<dd><p>
539N/A Use [do not use] TCP when querying name servers. The default
996N/A behavior is to use UDP unless an AXFR or IXFR query is
732N/A requested, in
732N/A which case a TCP connection is used.
732N/A </p></dd>
582N/A<dt><span class="term"><code class="option">+[no]vc</code></span></dt>
582N/A<dd><p>
582N/A Use [do not use] TCP when querying name servers. This alternate
582N/A syntax to <em class="parameter"><code>+[no]tcp</code></em> is
926N/A provided for backwards
582N/A compatibility. The "vc" stands for "virtual circuit".
582N/A </p></dd>
582N/A<dt><span class="term"><code class="option">+[no]ignore</code></span></dt>
938N/A<dd><p>
581N/A Ignore truncation in UDP responses instead of retrying with TCP.
581N/A By
581N/A default, TCP retries are performed.
988N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+domain=somename</code></span></dt>
789N/A<dd><p>
581N/A Set the search list to contain the single domain
581N/A <em class="parameter"><code>somename</code></em>, as if specified in
581N/A a
581N/A <span><strong class="command">domain</strong></span> directive in
581N/A <code class="filename">/etc/resolv.conf</code>, and enable
581N/A search list
581N/A processing as if the <em class="parameter"><code>+search</code></em>
581N/A option were given.
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]search</code></span></dt>
581N/A<dd><p>
581N/A Use [do not use] the search list defined by the searchlist or
581N/A domain
581N/A directive in <code class="filename">resolv.conf</code> (if
581N/A any).
581N/A The search list is not used by default.
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]showsearch</code></span></dt>
581N/A<dd><p>
581N/A Perform [do not perform] a search showing intermediate
581N/A results.
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]defname</code></span></dt>
581N/A<dd><p>
581N/A Deprecated, treated as a synonym for <em class="parameter"><code>+[no]search</code></em>
581N/A </p></dd>
988N/A<dt><span class="term"><code class="option">+[no]aaonly</code></span></dt>
988N/A<dd><p>
988N/A Sets the "aa" flag in the query.
988N/A </p></dd>
988N/A<dt><span class="term"><code class="option">+[no]aaflag</code></span></dt>
988N/A<dd><p>
988N/A A synonym for <em class="parameter"><code>+[no]aaonly</code></em>.
988N/A </p></dd>
988N/A<dt><span class="term"><code class="option">+[no]adflag</code></span></dt>
988N/A<dd><p>
988N/A Set [do not set] the AD (authentic data) bit in the
988N/A query. This requests the server to return whether
581N/A all of the answer and authority sections have all
784N/A been validated as secure according to the security
590N/A policy of the server. AD=1 indicates that all records
581N/A have been validated as secure and the answer is not
581N/A from a OPT-OUT range. AD=0 indicate that some part
581N/A of the answer was insecure or not validated. This
732N/A bit is set by default.
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]cdflag</code></span></dt>
581N/A<dd><p>
934N/A Set [do not set] the CD (checking disabled) bit in the query.
934N/A This
931N/A requests the server to not perform DNSSEC validation of
931N/A responses.
931N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]cl</code></span></dt>
581N/A<dd><p>
581N/A Display [do not display] the CLASS when printing the record.
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]ttlid</code></span></dt>
581N/A<dd><p>
581N/A Display [do not display] the TTL when printing the record.
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]recurse</code></span></dt>
581N/A<dd><p>
594N/A Toggle the setting of the RD (recursion desired) bit
581N/A in the query. This bit is set by default, which means
581N/A <span><strong class="command">dig</strong></span> normally sends recursive
581N/A queries. Recursion is automatically disabled when
581N/A the <em class="parameter"><code>+nssearch</code></em> or
581N/A <em class="parameter"><code>+trace</code></em> query options are used.
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]nssearch</code></span></dt>
581N/A<dd><p>
581N/A When this option is set, <span><strong class="command">dig</strong></span>
581N/A attempts to find the
581N/A authoritative name servers for the zone containing the name
858N/A being
858N/A looked up and display the SOA record that each name server has
858N/A for the
858N/A zone.
858N/A </p></dd>
858N/A<dt><span class="term"><code class="option">+[no]trace</code></span></dt>
858N/A<dd>
448N/A<p>
448N/A Toggle tracing of the delegation path from the root
448N/A name servers for the name being looked up. Tracing
448N/A is disabled by default. When tracing is enabled,
448N/A <span><strong class="command">dig</strong></span> makes iterative queries to
448N/A resolve the name being looked up. It will follow
448N/A referrals from the root servers, showing the answer
988N/A from each server that was used to resolve the lookup.
526N/A </p>
448N/A<p>
502N/A <span><strong class="command">+dnssec</strong></span> is also set when +trace is
581N/A set to better emulate the default queries from a nameserver.
792N/A </p>
709N/A</dd>
581N/A<dt><span class="term"><code class="option">+[no]cmd</code></span></dt>
926N/A<dd><p>
926N/A Toggles the printing of the initial comment in the output
926N/A identifying
926N/A the version of <span><strong class="command">dig</strong></span> and the query
926N/A options that have
926N/A been applied. This comment is printed by default.
926N/A </p></dd>
926N/A<dt><span class="term"><code class="option">+[no]short</code></span></dt>
926N/A<dd><p>
581N/A Provide a terse answer. The default is to print the answer in a
693N/A verbose form.
581N/A </p></dd>
926N/A<dt><span class="term"><code class="option">+[no]identify</code></span></dt>
581N/A<dd><p>
926N/A Show [or do not show] the IP address and port number that
926N/A supplied the
581N/A answer when the <em class="parameter"><code>+short</code></em> option
1007N/A is enabled. If
581N/A short form answers are requested, the default is not to show the
598N/A source address and port number of the server that provided the
581N/A answer.
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+[no]comments</code></span></dt>
581N/A<dd><p>
581N/A Toggle the display of comment lines in the output. The default
617N/A is to print comments.
617N/A </p></dd>
644N/A<dt><span class="term"><code class="option">+[no]rrcomments</code></span></dt>
886N/A<dd><p>
886N/A Toggle the display of per-record comments in the output (for
1008N/A example, human-readable key information about DNSKEY records).
1017N/A The default is not to print record comments unless multiline
581N/A mode is active.
891N/A </p></dd>
941N/A<dt><span class="term"><code class="option">+[no]crypto</code></span></dt>
581N/A<dd><p>
581N/A Toggle the display of cryptographic fields in DNSSEC records.
581N/A The contents of these field are unnecessary to debug most DNSSEC
581N/A validation failures and removing them makes it easier to see
581N/A the common failures. The default is to display the fields.
581N/A When omitted they are replaced by the string "[omitted]" or
581N/A in the DNSKEY case the key id is displayed as the replacement,
581N/A e.g. "[ key id = value ]".
581N/A </p></dd>
581N/A<dt><span class="term"><code class="option">+split=W</code></span></dt>
581N/A<dd><p>
993N/A Split long hex- or base64-formatted fields in resource
581N/A records into chunks of <em class="parameter"><code>W</code></em> characters
581N/A (where <em class="parameter"><code>W</code></em> is rounded up to the nearest
581N/A multiple of 4).
581N/A <em class="parameter"><code>+nosplit</code></em> or
873N/A <em class="parameter"><code>+split=0</code></em> causes fields not to be
873N/A split at all. The default is 56 characters, or 44 characters
873N/A when multiline mode is active.
873N/A </p></dd>
873N/A<dt><span class="term"><code class="option">+[no]stats</code></span></dt>
873N/A<dd><p>
948N/A This query option toggles the printing of statistics: when the
948N/A query
581N/A was made, the size of the reply and so on. The default
581N/A behavior is
581N/A to print the query statistics.
655N/A </p></dd>
873N/A<dt><span class="term"><code class="option">+[no]qr</code></span></dt>
873N/A<dd><p>
873N/A Print [do not print] the query as it is sent.
873N/A By default, the query is not printed.
448N/A </p></dd>
448N/A<dt><span class="term"><code class="option">+[no]question</code></span></dt>
838N/A<dd><p>
Print [do not print] the question section of a query when an
answer is
returned. The default is to print the question section as a
comment.
</p></dd>
<dt><span class="term"><code class="option">+[no]answer</code></span></dt>
<dd><p>
Display [do not display] the answer section of a reply. The
default
is to display it.
</p></dd>
<dt><span class="term"><code class="option">+[no]authority</code></span></dt>
<dd><p>
Display [do not display] the authority section of a reply. The
default is to display it.
</p></dd>
<dt><span class="term"><code class="option">+[no]additional</code></span></dt>
<dd><p>
Display [do not display] the additional section of a reply.
The default is to display it.
</p></dd>
<dt><span class="term"><code class="option">+[no]all</code></span></dt>
<dd><p>
Set or clear all display flags.
</p></dd>
<dt><span class="term"><code class="option">+time=T</code></span></dt>
<dd><p>
Sets the timeout for a query to
<em class="parameter"><code>T</code></em> seconds. The default
timeout is 5 seconds.
An attempt to set <em class="parameter"><code>T</code></em> to less
than 1 will result
in a query timeout of 1 second being applied.
</p></dd>
<dt><span class="term"><code class="option">+tries=T</code></span></dt>
<dd><p>
Sets the number of times to try UDP queries to server to
<em class="parameter"><code>T</code></em> instead of the default, 3.
If
<em class="parameter"><code>T</code></em> is less than or equal to
zero, the number of
tries is silently rounded up to 1.
</p></dd>
<dt><span class="term"><code class="option">+retry=T</code></span></dt>
<dd><p>
Sets the number of times to retry UDP queries to server to
<em class="parameter"><code>T</code></em> instead of the default, 2.
Unlike
<em class="parameter"><code>+tries</code></em>, this does not include
the initial
query.
</p></dd>
<dt><span class="term"><code class="option">+ndots=D</code></span></dt>
<dd><p>
Set the number of dots that have to appear in
<em class="parameter"><code>name</code></em> to <em class="parameter"><code>D</code></em> for it to be
considered absolute. The default value is that defined using
the
ndots statement in <code class="filename">/etc/resolv.conf</code>, or 1 if no
ndots statement is present. Names with fewer dots are
interpreted as
relative names and will be searched for in the domains listed in
the
<code class="option">search</code> or <code class="option">domain</code> directive in
<code class="filename">/etc/resolv.conf</code>.
</p></dd>
<dt><span class="term"><code class="option">+bufsize=B</code></span></dt>
<dd><p>
Set the UDP message buffer size advertised using EDNS0 to
<em class="parameter"><code>B</code></em> bytes. The maximum and minimum sizes
of this buffer are 65535 and 0 respectively. Values outside
this range are rounded up or down appropriately.
Values other than zero will cause a EDNS query to be sent.
</p></dd>
<dt><span class="term"><code class="option">+edns=#</code></span></dt>
<dd><p>
Specify the EDNS version to query with. Valid values
are 0 to 255. Setting the EDNS version will cause
a EDNS query to be sent. <code class="option">+noedns</code>
clears the remembered EDNS version. EDNS is set to
0 by default.
</p></dd>
<dt><span class="term"><code class="option">+[no]multiline</code></span></dt>
<dd><p>
Print records like the SOA records in a verbose multi-line
format with human-readable comments. The default is to print
each record on a single line, to facilitate machine parsing
of the <span><strong class="command">dig</strong></span> output.
</p></dd>
<dt><span class="term"><code class="option">+[no]onesoa</code></span></dt>
<dd><p>
Print only one (starting) SOA record when performing
an AXFR. The default is to print both the starting and
ending SOA records.
</p></dd>
<dt><span class="term"><code class="option">+[no]fail</code></span></dt>
<dd><p>
Do not try the next server if you receive a SERVFAIL. The
default is
to not try the next server which is the reverse of normal stub
resolver
behavior.
</p></dd>
<dt><span class="term"><code class="option">+[no]besteffort</code></span></dt>
<dd><p>
Attempt to display the contents of messages which are malformed.
The default is to not display malformed answers.
</p></dd>
<dt><span class="term"><code class="option">+[no]dnssec</code></span></dt>
<dd><p>
Requests DNSSEC records be sent by setting the DNSSEC OK bit
(DO)
in the OPT record in the additional section of the query.
</p></dd>
<dt><span class="term"><code class="option">+[no]sigchase</code></span></dt>
<dd><p>
Chase DNSSEC signature chains. Requires dig be compiled with
-DDIG_SIGCHASE.
</p></dd>
<dt><span class="term"><code class="option">+trusted-key=####</code></span></dt>
<dd>
<p>
Specifies a file containing trusted keys to be used with
<code class="option">+sigchase</code>. Each DNSKEY record must be
on its own line.
</p>
<p>
If not specified, <span><strong class="command">dig</strong></span> will look for
<code class="filename">/etc/trusted-key.key</code> then
<code class="filename">trusted-key.key</code> in the current directory.
</p>
<p>
Requires dig be compiled with -DDIG_SIGCHASE.
</p>
</dd>
<dt><span class="term"><code class="option">+[no]topdown</code></span></dt>
<dd><p>
When chasing DNSSEC signature chains perform a top-down
validation.
Requires dig be compiled with -DDIG_SIGCHASE.
</p></dd>
<dt><span class="term"><code class="option">+[no]nsid</code></span></dt>
<dd><p>
Include an EDNS name server ID request when sending a query.
</p></dd>
<dt><span class="term"><code class="option">+[no]keepopen</code></span></dt>
<dd><p>
Keep the TCP socket open between queries and reuse it rather
than creating a new TCP socket for each lookup. The default
is <code class="option">+nokeepopen</code>.
</p></dd>
</dl></div>
<p>
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2667056"></a><h2>MULTIPLE QUERIES</h2>
<p>
The BIND 9 implementation of <span><strong class="command">dig </strong></span>
supports
specifying multiple queries on the command line (in addition to
supporting the <code class="option">-f</code> batch file option). Each of those
queries can be supplied with its own set of flags, options and query
options.
</p>
<p>
In this case, each <em class="parameter"><code>query</code></em> argument
represent an
individual query in the command-line syntax described above. Each
consists of any of the standard options and flags, the name to be
looked up, an optional query type and class and any query options that
should be applied to that query.
</p>
<p>
A global set of query options, which should be applied to all queries,
can also be supplied. These global query options must precede the
first tuple of name, class, type, options, flags, and query options
supplied on the command line. Any global query options (except
the <code class="option">+[no]cmd</code> option) can be
overridden by a query-specific set of query options. For example:
</p>
<pre class="programlisting">
dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
</pre>
<p>
shows how <span><strong class="command">dig</strong></span> could be used from the
command line
to make three lookups: an ANY query for <code class="literal">www.isc.org</code>, a
reverse lookup of 127.0.0.1 and a query for the NS records of
<code class="literal">isc.org</code>.
A global query option of <em class="parameter"><code>+qr</code></em> is
applied, so
that <span><strong class="command">dig</strong></span> shows the initial query it made
for each
lookup. The final query has a local query option of
<em class="parameter"><code>+noqr</code></em> which means that <span><strong class="command">dig</strong></span>
will not print the initial query when it looks up the NS records for
<code class="literal">isc.org</code>.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2667209"></a><h2>IDN SUPPORT</h2>
<p>
If <span><strong class="command">dig</strong></span> has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
<span><strong class="command">dig</strong></span> appropriately converts character encoding of
domain name before sending a request to DNS server or displaying a
reply from the server.
If you'd like to turn off the IDN support for some reason, defines
the <code class="envar">IDN_DISABLE</code> environment variable.
The IDN support is disabled if the variable is set when
<span><strong class="command">dig</strong></span> runs.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2667238"></a><h2>FILES</h2>
<p><code class="filename">/etc/resolv.conf</code>
</p>
<p><code class="filename">${HOME}/.digrc</code>
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2667259"></a><h2>SEE ALSO</h2>
<p><span class="citerefentry"><span class="refentrytitle">host</span>(1)</span>,
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
<span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
<em class="citetitle">RFC1035</em>.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2667297"></a><h2>BUGS</h2>
<p>
There are probably too many query options.
</p>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="Bv9ARM.ch10.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch10.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.host.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Manual pages�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�host</td>
</tr>
</table>
</div>
</body>
</html>