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