Gecko [ nbspublicschool.com ]

Name	Size	Permission
sample	[ DIR ]	drwxr-xr-x
Bv9ARM.ch01.html	26.11 KB	-rw-r--r--
Bv9ARM.ch02.html	7.18 KB	-rw-r--r--
Bv9ARM.ch03.html	30.38 KB	-rw-r--r--
Bv9ARM.ch04.html	129.65 KB	-rw-r--r--
Bv9ARM.ch05.html	6.29 KB	-rw-r--r--
Bv9ARM.ch06.html	684.15 KB	-rw-r--r--
Bv9ARM.ch07.html	19.56 KB	-rw-r--r--
Bv9ARM.ch08.html	6.32 KB	-rw-r--r--
Bv9ARM.ch09.html	10.27 KB	-rw-r--r--
Bv9ARM.ch10.html	6.92 KB	-rw-r--r--
Bv9ARM.ch11.html	53.24 KB	-rw-r--r--
Bv9ARM.ch12.html	20.45 KB	-rw-r--r--
Bv9ARM.ch13.html	9.88 KB	-rw-r--r--
Bv9ARM.html	29.71 KB	-rw-r--r--
Bv9ARM.pdf	1.24 MB	-rw-r--r--
CHANGES	528.76 KB	-rw-r--r--
README	22.46 KB	-rw-r--r--
isc-logo.pdf	281.24 KB	-rw-r--r--
man.arpaname.html	3.01 KB	-rw-r--r--
man.ddns-confgen.html	9.49 KB	-rw-r--r--
man.delv.html	23.87 KB	-rw-r--r--
man.dig.html	40.63 KB	-rw-r--r--
man.dnssec-checkds.html	5.35 KB	-rw-r--r--
man.dnssec-coverage.html	11.35 KB	-rw-r--r--
man.dnssec-dsfromkey.html	9.68 KB	-rw-r--r--
man.dnssec-importkey.html	9.58 KB	-rw-r--r--
man.dnssec-keyfromlabel.html	19.12 KB	-rw-r--r--
man.dnssec-keygen.html	22.31 KB	-rw-r--r--
man.dnssec-keymgr.html	15.15 KB	-rw-r--r--
man.dnssec-revoke.html	5.62 KB	-rw-r--r--
man.dnssec-settime.html	14.55 KB	-rw-r--r--
man.dnssec-signzone.html	30.69 KB	-rw-r--r--
man.dnssec-verify.html	7.43 KB	-rw-r--r--
man.dnstap-read.html	4.39 KB	-rw-r--r--
man.genrandom.html	4.13 KB	-rw-r--r--
man.host.html	12.74 KB	-rw-r--r--
man.isc-hmac-fixup.html	4.6 KB	-rw-r--r--
man.lwresd.html	12.45 KB	-rw-r--r--
man.mdig.html	23.18 KB	-rw-r--r--
man.named-checkconf.html	6.77 KB	-rw-r--r--
man.named-checkzone.html	20.21 KB	-rw-r--r--
man.named-journalprint.html	4.2 KB	-rw-r--r--
man.named-nzd2nzf.html	3.86 KB	-rw-r--r--
man.named-rrchecker.html	4.21 KB	-rw-r--r--
man.named.conf.html	73.42 KB	-rw-r--r--
man.named.html	19.07 KB	-rw-r--r--
man.nsec3hash.html	4.17 KB	-rw-r--r--
man.nslookup.html	14.49 KB	-rw-r--r--
man.nsupdate.html	28.11 KB	-rw-r--r--
man.pkcs11-destroy.html	5.57 KB	-rw-r--r--
man.pkcs11-keygen.html	7.13 KB	-rw-r--r--
man.pkcs11-list.html	5.46 KB	-rw-r--r--
man.pkcs11-tokens.html	3.73 KB	-rw-r--r--
man.rndc-confgen.html	11.48 KB	-rw-r--r--
man.rndc.conf.html	10.17 KB	-rw-r--r--
man.rndc.html	39.89 KB	-rw-r--r--
named.conf.default	1.76 KB	-rw-r--r--
notes.html	7.31 KB	-rw-r--r--
notes.pdf	50.96 KB	-rw-r--r--

Code Editor : man.dig.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dig</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="next" href="man.mdig.html" title="mdig">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">dig</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="Bv9ARM.ch13.html">Prev</a>�</td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right">�<a accesskey="n" href="man.mdig.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
<div class="refentry">
<a name="man.dig"></a><div class="titlepage"></div>

<div class="refnamediv">
<h2>Name</h2>

 dig
 &#8212; DNS lookup utility
 
</div>

<div class="refsynopsisdiv">
<h2>Synopsis</h2>
 <div class="cmdsynopsis">
 <code class="command">dig</code> 
 [@server]
 [<code class="option">-b <code>address</code></code>]
 [<code class="option">-c <code>class</code></code>]
 [<code class="option">-f <code>filename</code></code>]
 [<code class="option">-k <code>filename</code></code>]
 [<code class="option">-m</code>]
 [<code class="option">-p <code>port#</code></code>]
 [<code class="option">-q <code>name</code></code>]
 [<code class="option">-t <code>type</code></code>]
 [<code class="option">-v</code>]
 [<code class="option">-x <code>addr</code></code>]
 [<code class="option">-y <code>[hmac:]name:key</code></code>]
 [
	[<code class="option">-4</code>]
	 | [<code class="option">-6</code>]
 ]
 [name]
 [type]
 [class]
 [queryopt...]
 </div>

<div class="cmdsynopsis">
 <code class="command">dig</code> 
 [global-queryopt...]
 [query...]
 </div>
 </div>

<div class="refsection">
<a name="id-1.14.2.7"></a><h2>DESCRIPTION</h2>

dig is a flexible tool
 for interrogating DNS name servers. It performs DNS lookups and
 displays the answers that are returned from the name server(s) that
 were queried. Most DNS administrators use dig to
 troubleshoot DNS problems because of its flexibility, ease of use and
 clarity of output. Other lookup tools tend to have less functionality
 than dig.

Although dig is normally used with
 command-line
 arguments, it also has a batch mode of operation for reading lookup
 requests from a file. A brief summary of its command-line arguments
 and options is printed when the <code class="option">-h</code> option is given.
 Unlike earlier versions, the BIND 9 implementation of
 dig allows multiple lookups to be issued
 from the
 command line.

Unless it is told to query a specific name server,
 dig will try each of the servers listed in
 <code class="filename">/etc/resolv.conf</code>. If no usable server addresses
 are found, dig will send the query to the local
 host.

When no command line arguments or options are given,
 dig will perform an NS query for "." (the root).

It is possible to set per-user defaults for dig via
 <code class="filename">${HOME}/.digrc</code>. This file is read and
 any options in it
 are applied before the command line arguments.

The IN and CH class names overlap with the IN and CH top level
 domain names. Either use the <code class="option">-t</code> and
 <code class="option">-c</code> options to specify the type and class,
 use the <code class="option">-q</code> the specify the domain name, or
 use "IN." and "CH." when looking up these top level domains.

</div>

<div class="refsection">
<a name="id-1.14.2.8"></a><h2>SIMPLE USAGE</h2>

A typical invocation of dig looks like:
 
<pre class="programlisting"> dig @server name type </pre>

 where:

<div class="variablelist"><dl class="variablelist">
<dt><code class="constant">server</code></dt>
<dd>
	 
	 is the name or IP address of the name server to query. This
	 can be an IPv4 address in dotted-decimal notation or an IPv6
	 address in colon-delimited notation. When the supplied
	 <code>server</code> argument is a hostname,
	 dig resolves that name before querying
	 that name server.
	 
	 
	 If no <code>server</code> argument is
	 provided, dig consults
	 <code class="filename">/etc/resolv.conf</code>; if an
	 address is found there, it queries the name server at
	 that address. If either of the <code class="option">-4</code> or
	 <code class="option">-6</code> options are in use, then
	 only addresses for the corresponding transport
	 will be tried. If no usable addresses are found,
	 dig will send the query to the
	 local host. The reply from the name server that
	 responds is displayed.
	 
	 </dd>
<dt><code class="constant">name</code></dt>
<dd>
	 
	 is the name of the resource record that is to be looked up.
	 
	 </dd>
<dt><code class="constant">type</code></dt>
<dd>
	 
	 indicates what type of query is required &#8212;
	 ANY, A, MX, SIG, etc.
	 <code>type</code> can be any valid query
	 type. If no
	 <code>type</code> argument is supplied,
	 dig will perform a lookup for an
	 A record.
	 
	 </dd>
</dl></div>

</div>

<div class="refsection">
<a name="id-1.14.2.9"></a><h2>OPTIONS</h2>

<div class="variablelist"><dl class="variablelist">
<dt>-4</dt>
<dd>
	 
	 Use IPv4 only.
	 
	</dd>
<dt>-6</dt>
<dd>
	 
	 Use IPv6 only.
	 
	</dd>
<dt>-b <code>address[#port]</code></dt>
<dd>
	 
	 Set the source IP address of the query.
	 The <code>address</code> must be a valid address on
	 one of the host's network interfaces, or "0.0.0.0" or "::". An
	 optional port may be specified by appending "#&lt;port&gt;"
	 
	</dd>
<dt>-c <code>class</code></dt>
<dd>
	 
	 Set the query class. The
	 default <code>class</code> is IN; other classes
	 are HS for Hesiod records or CH for Chaosnet records.
	 
	</dd>
<dt>-f <code>file</code></dt>
<dd>
	 
	 Batch mode: dig reads a list of lookup
	 requests to process from the
	 given <code>file</code>. Each line in the file
	 should be organized in the same way they would be
	 presented as queries to
	 dig using the command-line interface.
	 
	</dd>
<dt>-i</dt>
<dd>
	 
	 Do reverse IPv6 lookups using the obsolete RFC 1886 IP6.INT
	 domain, which is no longer in use. Obsolete bit string
	 label queries (RFC 2874) are not attempted.
	 
	</dd>
<dt>-k <code>keyfile</code></dt>
<dd>
	 
	 Sign queries using TSIG using a key read from the given file.
	 Key files can be generated using
	 
	 tsig-keygen(8)
	 .
	 When using TSIG authentication with dig,
	 the name server that is queried needs to know the key and
	 algorithm that is being used. In BIND, this is done by
	 providing appropriate key
	 and server statements in
	 <code class="filename">named.conf</code>.
	 
	</dd>
<dt>-m</dt>
<dd>
	 
	 Enable memory usage debugging.
	 
	 
	</dd>
<dt>-p <code>port</code></dt>
<dd>
	 
	 Send the query to a non-standard port on the server,
	 instead of the default port 53. This option would be used
	 to test a name server that has been configured to listen
	 for queries on a non-standard port number.
	 
	</dd>
<dt>-q <code>name</code></dt>
<dd>
	 
	 The domain name to query. This is useful to distinguish
	 the <code>name</code> from other arguments.
	 
	</dd>
<dt>-t <code>type</code></dt>
<dd>
	 
	 The resource record type to query. It can be any valid query
	 type. If it is a resource record type supported in BIND 9, it
	 can be given by the type mnemonic (such as "NS" or "AAAA").
	 The default query type is "A", unless the <code class="option">-x</code>
	 option is supplied to indicate a reverse lookup. A zone
	 transfer can be requested by specifying a type of AXFR. When
	 an incremental zone transfer (IXFR) is required, set the
	 <code>type</code> to <code class="literal">ixfr=N</code>.
	 The incremental zone transfer will contain the changes
	 made to the zone since the serial number in the zone's SOA
	 record was
	 <code>N</code>.
	 
	 
	 All resource record types can be expressed as "TYPEnn", where
	 "nn" is the number of the type. If the resource record type is
	 not supported in BIND 9, the result will be displayed as
	 described in RFC 3597.
	 
	</dd>
<dt>-u</dt>
<dd>
	 
	 Print query times in microseconds instead of milliseconds.
	 
	</dd>
<dt>-v</dt>
<dd>
	 
	 Print the version number and exit.
	 
	</dd>
<dt>-x <code>addr</code></dt>
<dd>
	 
	 Simplified reverse lookups, for mapping addresses to
	 names. The <code>addr</code> is an IPv4 address
	 in dotted-decimal notation, or a colon-delimited IPv6
	 address. When the <code class="option">-x</code> is used, there is no
	 need to provide
	 the <code>name</code>, <code>class</code>
	 and <code>type</code>
	 arguments. dig automatically performs a
	 lookup for a name like
	 <code class="literal">94.2.0.192.in-addr.arpa</code> and sets the
	 query type and class to PTR and IN respectively. IPv6
	 addresses are looked up using nibble format under the
	 IP6.ARPA domain (but see also the <code class="option">-i</code>
	 option).
	 
	</dd>
<dt>-y <code>[hmac:]keyname:secret</code></dt>
<dd>
	 
	 Sign queries using TSIG with the given authentication key.
	 <code>keyname</code> is the name of the key, and
	 <code>secret</code> is the base64 encoded shared secret.
	 <code>hmac</code> is the name of the key algorithm;
	 valid choices are <code class="literal">hmac-md5</code>,
	 <code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>,
	 <code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code>, or
	 <code class="literal">hmac-sha512</code>. If <code>hmac</code>
	 is not specified, the default is <code class="literal">hmac-md5</code>
	 or if MD5 was disabled <code class="literal">hmac-sha256</code>.
	 
	 
	 NOTE: You should use the <code class="option">-k</code> option and
	 avoid the <code class="option">-y</code> option, because
	 with <code class="option">-y</code> the shared secret is supplied as
	 a command line argument in clear text. This may be visible
	 in the output from
	 
	 ps(1)
	 
	 or in a history file maintained by the user's shell.
	 
	</dd>
</dl></div>
 </div>

<div class="refsection">
<a name="id-1.14.2.10"></a><h2>QUERY OPTIONS</h2>

dig
 provides a number of query options which affect
 the way in which lookups are made and the results displayed. Some of
 these set or reset flag bits in the query header, some determine which
 sections of the answer get printed, and others determine the timeout
 and retry strategies.

Each query option is identified by a keyword preceded by a plus sign
 (<code class="literal">+</code>). Some keywords set or reset an
 option. These may be preceded
 by the string <code class="literal">no</code> to negate the meaning of
 that keyword. Other
 keywords assign values to options like the timeout interval. They
 have the form <code class="option">+keyword=value</code>.
 Keywords may be abbreviated, provided the abbreviation is
 unambiguous; for example, <code class="literal">+cd</code> is equivalent
 to <code class="literal">+cdflag</code>.
 The query options are:

<div class="variablelist"><dl class="variablelist">
<dt><code class="option">+[no]aaflag</code></dt>
<dd>
	 
	 A synonym for <code>+[no]aaonly</code>.
	 
	 </dd>
<dt><code class="option">+[no]aaonly</code></dt>
<dd>
	 
	 Sets the "aa" flag in the query.
	 
	 </dd>
<dt><code class="option">+[no]additional</code></dt>
<dd>
	 
	 Display [do not display] the additional section of a
	 reply. The default is to display it.
	 
	 </dd>
<dt><code class="option">+[no]adflag</code></dt>
<dd>
	 
	 Set [do not set] the AD (authentic data) bit in the
	 query. This requests the server to return whether
	 all of the answer and authority sections have all
	 been validated as secure according to the security
	 policy of the server. AD=1 indicates that all records
	 have been validated as secure and the answer is not
	 from a OPT-OUT range. AD=0 indicate that some part
	 of the answer was insecure or not validated. This
	 bit is set by default.
	 
	 </dd>
<dt><code class="option">+[no]all</code></dt>
<dd>
	 
	 Set or clear all display flags.
	 
	 </dd>
<dt><code class="option">+[no]answer</code></dt>
<dd>
	 
	 Display [do not display] the answer section of a
	 reply. The default is to display it.
	 
	 </dd>
<dt><code class="option">+[no]authority</code></dt>
<dd>
	 
	 Display [do not display] the authority section of a
	 reply. The default is to display it.
	 
	 </dd>
<dt><code class="option">+[no]badcookie</code></dt>
<dd>
	 
	 Retry lookup with the new server cookie if a
	 BADCOOKIE response is received.
	 
	 </dd>
<dt><code class="option">+[no]besteffort</code></dt>
<dd>
	 
	 Attempt to display the contents of messages which are
	 malformed. The default is to not display malformed
	 answers.
	 
	 </dd>
<dt><code class="option">+bufsize=B</code></dt>
<dd>
	 
	 Set the UDP message buffer size advertised using EDNS0
	 to <code>B</code> 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.
	 
	 </dd>
<dt><code class="option">+[no]cdflag</code></dt>
<dd>
	 
	 Set [do not set] the CD (checking disabled) bit in
	 the query. This requests the server to not perform
	 DNSSEC validation of responses.
	 
	 </dd>
<dt><code class="option">+[no]class</code></dt>
<dd>
	 
	 Display [do not display] the CLASS when printing the
	 record.
	 
	 </dd>
<dt><code class="option">+[no]cmd</code></dt>
<dd>
	 
	 Toggles the printing of the initial comment in the
	 output identifying the version of dig
	 and the query options that have been applied. This
	 comment is printed by default.
	 
	 </dd>
<dt><code class="option">+[no]comments</code></dt>
<dd>
	 
	 Toggle the display of comment lines in the output.
	 The default is to print comments.
	 
	 </dd>
<dt><code class="option">+[no]cookie[=####]</code></dt>
<dd>
	 
	 Send a COOKIE EDNS option, with optional
	 value. Replaying a COOKIE from a previous response will
	 allow the server to identify a previous client. The
	 default is <code class="option">+cookie</code>.
	 
	 
	 +cookie is also set when +trace
	 is set to better emulate the default queries from a
	 nameserver.
	 
	 </dd>
<dt><code class="option">+[no]crypto</code></dt>
<dd>
	 
	 Toggle the display of cryptographic fields in DNSSEC
	 records. The contents of these field are unnecessary
	 to debug most DNSSEC validation failures and removing
	 them makes it easier to see the common failures. The
	 default is to display the fields. When omitted they
	 are replaced by the string "[omitted]" or in the
	 DNSKEY case the key id is displayed as the replacement,
	 e.g. "[ key id = value ]".
	 
	 </dd>
<dt><code class="option">+[no]defname</code></dt>
<dd>
	 
	 Deprecated, treated as a synonym for
	 <code>+[no]search</code>
	 
	 </dd>
<dt><code class="option">+[no]dnssec</code></dt>
<dd>
	 
	 Requests DNSSEC records be sent by setting the DNSSEC
	 OK bit (DO) in the OPT record in the additional section
	 of the query.
	 
	 </dd>
<dt><code class="option">+domain=somename</code></dt>
<dd>
	 
	 Set the search list to contain the single domain
	 <code>somename</code>, as if specified in
	 a domain directive in
	 <code class="filename">/etc/resolv.conf</code>, and enable
	 search list processing as if the
	 <code>+search</code> option were given.
	 
	 </dd>
<dt><code class="option">+dscp=value</code></dt>
<dd>
	 
	 Set the DSCP code point to be used when sending the
	 query. Valid DSCP code points are in the range
	 [0..63]. By default no code point is explicitly set.
	 
	 </dd>
<dt><code class="option">+[no]edns[=#]</code></dt>
<dd>
	 
	 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.
	 
	 </dd>
<dt><code class="option">+[no]ednsflags[=#]</code></dt>
<dd>
	 
	 Set the must-be-zero EDNS flags bits (Z bits) to the
	 specified value. Decimal, hex and octal encodings are
	 accepted. Setting a named flag (e.g. DO) will silently be
	 ignored. By default, no Z bits are set.
	 
	 </dd>
<dt><code class="option">+[no]ednsnegotiation</code></dt>
<dd>
	 
	 Enable / disable EDNS version negotiation. By default
	 EDNS version negotiation is enabled.
	 
	 </dd>
<dt><code class="option">+[no]ednsopt[=code[:value]]</code></dt>
<dd>
	 
	 Specify EDNS option with code point <code class="option">code</code>
	 and optionally payload of <code class="option">value</code> as a
	 hexadecimal string. <code class="option">code</code> can be
	 either an EDNS option name (for example,
	 <code class="literal">NSID</code> or <code class="literal">ECS</code>),
	 or an arbitrary numeric value. <code class="option">+noednsopt</code>
	 clears the EDNS options to be sent.
	 
	 </dd>
<dt><code class="option">+[no]expire</code></dt>
<dd>
	 
	 Send an EDNS Expire option.
	 
	 </dd>
<dt><code class="option">+[no]fail</code></dt>
<dd>
	 
	 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.
	 
	 </dd>
<dt><code class="option">+[no]header-only</code></dt>
<dd>
	 
	 Send a query with a DNS header without a question section.
	 The default is to add a question section. The query type
	 and query name are ignored when this is set.
	 
	 </dd>
<dt><code class="option">+[no]identify</code></dt>
<dd>
	 
	 Show [or do not show] the IP address and port number
	 that supplied the answer when the
	 <code>+short</code> option is enabled. If
	 short form answers are requested, the default is not
	 to show the source address and port number of the
	 server that provided the answer.
	 
	 </dd>
<dt><code class="option">+[no]idnin</code></dt>
<dd>
	 
	 Process [do not process] IDN domain names on input.
	 This requires IDN SUPPORT to have been enabled at
	 compile time. The default is to process IDN input.
	 
	 </dd>
<dt><code class="option">+[no]idnout</code></dt>
<dd>
	 
	 Convert [do not convert] puny code on output.
	 This requires IDN SUPPORT to have been enabled at
	 compile time. The default is to convert output.
	 
	 </dd>
<dt><code class="option">+[no]ignore</code></dt>
<dd>
	 
	 Ignore truncation in UDP responses instead of retrying
	 with TCP. By default, TCP retries are performed.
	 
	 </dd>
<dt><code class="option">+[no]keepopen</code></dt>
<dd>
	 
	 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>.
	 
	 </dd>
<dt><code class="option">+[no]mapped</code></dt>
<dd>
	 
	 Allow mapped IPv4 over IPv6 addresses to be used. The
	 default is <code class="option">+mapped</code>.
	 
	 </dd>
<dt><code class="option">+[no]multiline</code></dt>
<dd>
	 
	 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 dig
	 output.
	 
	 </dd>
<dt><code class="option">+ndots=D</code></dt>
<dd>
	 
	 Set the number of dots that have to appear in
	 <code>name</code> to <code>D</code>
	 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> if
	 <code class="option">+search</code> is set.
	 
	 </dd>
<dt><code class="option">+[no]nsid</code></dt>
<dd>
	 
	 Include an EDNS name server ID request when sending
	 a query.
	 
	 </dd>
<dt><code class="option">+[no]nssearch</code></dt>
<dd>
	 
	 When this option is set, dig
	 attempts to find the authoritative name servers for
	 the zone containing the name being looked up and
	 display the SOA record that each name server has for
	 the zone.
	 
	 </dd>
<dt><code class="option">+[no]onesoa</code></dt>
<dd>
	 
	 Print only one (starting) SOA record when performing
	 an AXFR. The default is to print both the starting
	 and ending SOA records.
	 
	 </dd>
<dt><code class="option">+[no]opcode=value</code></dt>
<dd>
	 
	 Set [restore] the DNS message opcode to the specified
	 value. The default value is QUERY (0).
	 
	 </dd>
<dt><code class="option">+[no]qr</code></dt>
<dd>
	 
	 Print [do not print] the query as it is sent. By
	 default, the query is not printed.
	 
	 </dd>
<dt><code class="option">+[no]question</code></dt>
<dd>
	 
	 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.
	 
	 </dd>
<dt><code class="option">+[no]rdflag</code></dt>
<dd>
	 
	 A synonym for <code>+[no]recurse</code>.
	 
	 </dd>
<dt><code class="option">+[no]recurse</code></dt>
<dd>
	 
	 Toggle the setting of the RD (recursion desired) bit
	 in the query. This bit is set by default, which means
	 dig normally sends recursive
	 queries. Recursion is automatically disabled when
	 the <code>+nssearch</code> or
	 <code>+trace</code> query options are used.
	 
	 </dd>
<dt><code class="option">+retry=T</code></dt>
<dd>
	 
	 Sets the number of times to retry UDP queries to
	 server to <code>T</code> instead of the
	 default, 2. Unlike <code>+tries</code>,
	 this does not include the initial query.
	 
	 </dd>
<dt><code class="option">+[no]rrcomments</code></dt>
<dd>
	 
	 Toggle the display of per-record comments in the
	 output (for example, human-readable key information
	 about DNSKEY records). The default is not to print
	 record comments unless multiline mode is active.
	 
	 </dd>
<dt><code class="option">+[no]search</code></dt>
<dd>
	 
	 Use [do not use] the search list defined by the
	 searchlist or domain directive in
	 <code class="filename">resolv.conf</code> (if any). The search
	 list is not used by default.
	 
	 
	 'ndots' from <code class="filename">resolv.conf</code> (default 1)
	 which may be overridden by <code>+ndots</code>
	 determines if the name will be treated as relative
	 or not and hence whether a search is eventually
	 performed or not.
	 
	 </dd>
<dt><code class="option">+[no]short</code></dt>
<dd>
	 
	 Provide a terse answer. The default is to print the
	 answer in a verbose form.
	 
	 </dd>
<dt><code class="option">+[no]showsearch</code></dt>
<dd>
	 
	 Perform [do not perform] a search showing intermediate
	 results.
	 
	 </dd>
<dt><code class="option">+[no]sigchase</code></dt>
<dd>
	 
	 Chase DNSSEC signature chains. Requires dig be compiled
	 with -DDIG_SIGCHASE. This feature is deprecated.
	 Use delv instead.
	 
	 </dd>
<dt><code class="option">+split=W</code></dt>
<dd>
	 
	 Split long hex- or base64-formatted fields in resource
	 records into chunks of <code>W</code>
	 characters (where <code>W</code> is rounded
	 up to the nearest multiple of 4).
	 <code>+nosplit</code> or
	 <code>+split=0</code> causes fields not to
	 be split at all. The default is 56 characters, or
	 44 characters when multiline mode is active.
	 
	 </dd>
<dt><code class="option">+[no]stats</code></dt>
<dd>
	 
	 This query option toggles the printing of statistics:
	 when the query was made, the size of the reply and
	 so on. The default behavior is to print the query
	 statistics.
	 
	 </dd>
<dt><code class="option">+[no]subnet=addr[/prefix-length]</code></dt>
<dd>
	 
	 Send (don't send) an EDNS Client Subnet option with the
	 specified IP address or network prefix.
	 
	 
 dig +subnet=0.0.0.0/0, or simply
 dig +subnet=0 for short, sends an EDNS
 CLIENT-SUBNET option with an empty address and a source
 prefix-length of zero, which signals a resolver that
 the client's address information must
 not be used when resolving
 this query.
	 
	 </dd>
<dt><code class="option">+[no]tcp</code></dt>
<dd>
	 
	 Use [do not use] TCP when querying name servers. The
	 default behavior is to use UDP unless a type
	 <code class="literal">any</code> or <code class="literal">ixfr=N</code>
	 query is requested, in which case the default is TCP.
	 AXFR queries always use TCP.
	 
	 </dd>
<dt><code class="option">+timeout=T</code></dt>
<dd>

Sets the timeout for a query to
	 <code>T</code> seconds. The default
	 timeout is 5 seconds.
	 An attempt to set <code>T</code> to less
	 than 1 will result
	 in a query timeout of 1 second being applied.
	 
	 </dd>
<dt><code class="option">+[no]topdown</code></dt>
<dd>
	 
	 When chasing DNSSEC signature chains perform a top-down
	 validation. Requires dig be compiled with -DDIG_SIGCHASE.
	 This feature is deprecated. Use delv instead.
	 
	 </dd>
<dt><code class="option">+[no]trace</code></dt>
<dd>
	 
	 Toggle tracing of the delegation path from the root
	 name servers for the name being looked up. Tracing
	 is disabled by default. When tracing is enabled,
	 dig makes iterative queries to
	 resolve the name being looked up. It will follow
	 referrals from the root servers, showing the answer
	 from each server that was used to resolve the lookup.
	 
	 If @server is also specified, it affects only the
	 initial query for the root zone name servers.
	 
	 +dnssec is also set when +trace
	 is set to better emulate the default queries from a
	 nameserver.
	 
	 </dd>
<dt><code class="option">+tries=T</code></dt>
<dd>
	 
	 Sets the number of times to try UDP queries to server
	 to <code>T</code> instead of the default,
	 3. If <code>T</code> is less than or equal
	 to zero, the number of tries is silently rounded up
	 to 1.
	 
	 </dd>
<dt><code class="option">+trusted-key=####</code></dt>
<dd>
	 
	 Specifies a file containing trusted keys to be used
	 with <code class="option">+sigchase</code>. Each DNSKEY record
	 must be on its own line.
	 
	 If not specified, dig will look
	 for <code class="filename">/etc/trusted-key.key</code> then
	 <code class="filename">trusted-key.key</code> in the current
	 directory.
	 
	 Requires dig be compiled with -DDIG_SIGCHASE.
	 This feature is deprecated. Use delv instead.
	 
	 </dd>
<dt><code class="option">+[no]ttlid</code></dt>
<dd>
	 
	 Display [do not display] the TTL when printing the
	 record.
	 
	 </dd>
<dt><code class="option">+[no]ttlunits</code></dt>
<dd>
	 
	 Display [do not display] the TTL in friendly human-readable
	 time units of "s", "m", "h", "d", and "w", representing
	 seconds, minutes, hours, days and weeks. Implies +ttlid.
	 
	 </dd>
<dt><code class="option">+[no]unknownformat</code></dt>
<dd>
	 
	 Print all RDATA in unknown RR type presentation format
	 (RFC 3597). The default is to print RDATA for known types
	 in the type's presentation format.
	 
	 </dd>
<dt><code class="option">+[no]vc</code></dt>
<dd>
	 
	 Use [do not use] TCP when querying name servers. This
	 alternate syntax to <code>+[no]tcp</code>
	 is provided for backwards compatibility. The "vc"
	 stands for "virtual circuit".
	 
	 </dd>
<dt><code class="option">+[no]zflag</code></dt>
<dd>
	 
	 Set [do not set] the last unassigned DNS header flag in a
	 DNS query. This flag is off by default.
	 
	 </dd>
</dl></div>

</div>

<div class="refsection">
<a name="id-1.14.2.11"></a><h2>MULTIPLE QUERIES</h2>

The BIND 9 implementation of dig 
 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.

In this case, each <code>query</code> 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.

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:
 
<pre class="programlisting">
dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
</pre>

 shows how dig 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 <code>+qr</code> is
 applied, so
 that dig shows the initial query it made
 for each
 lookup. The final query has a local query option of
 <code>+noqr</code> which means that dig
 will not print the initial query when it looks up the NS records for
 <code class="literal">isc.org</code>.

</div>

<div class="refsection">
<a name="id-1.14.2.12"></a><h2>IDN SUPPORT</h2>

If dig has been built with IDN (internationalized
 domain name) support, it can accept and display non-ASCII domain names.
 dig 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, use
 parameters <code>+noidnin</code> and
 <code>+noidnout</code>.
 
 </div>

<div class="refsection">
<a name="id-1.14.2.13"></a><h2>FILES</h2>

<code class="filename">/etc/resolv.conf</code>
 
 <code class="filename">${HOME}/.digrc</code>
 
 </div>

delv(1)
 ,
 
	host(1)
 ,
 
	named(8)
 ,
 
	dnssec-keygen(8)
 ,
 RFC 1035.
 
 </div>

There are probably too many query options.
 
 </div>

</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="Bv9ARM.ch13.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.mdig.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">�mdig
</td>
</tr>
</table>
</div>
BIND 9.11.4-P2 (Extended Support Version)
</body>
</html>

${this.title}

Code Editor : man.dig.html