head 1.2; access; symbols perseant-exfatfs-base-20240630:1.2 perseant-exfatfs:1.2.0.16 perseant-exfatfs-base:1.2 cjep_sun2x:1.2.0.14 cjep_sun2x-base:1.2 cjep_staticlib_x-base1:1.2 cjep_staticlib_x:1.2.0.12 cjep_staticlib_x-base:1.2 phil-wifi-20200421:1.2 phil-wifi-20200411:1.2 phil-wifi-20200406:1.2 pgoyette-compat-merge-20190127:1.2 pgoyette-compat-20190127:1.2 pgoyette-compat-20190118:1.2 pgoyette-compat-1226:1.2 pgoyette-compat-1126:1.2 pgoyette-compat-1020:1.2 pgoyette-compat-0930:1.2 pgoyette-compat-0906:1.2 pgoyette-compat-0728:1.2 pgoyette-compat-0625:1.2 pgoyette-compat-0521:1.2 pgoyette-compat-0502:1.2 pgoyette-compat-0422:1.2 pgoyette-compat-0415:1.2 pgoyette-compat-0407:1.2 pgoyette-compat-0330:1.2 pgoyette-compat-0322:1.2 pgoyette-compat-0315:1.2 pgoyette-compat:1.2.0.10 pgoyette-compat-base:1.2 perseant-stdc-iso10646:1.2.0.8 perseant-stdc-iso10646-base:1.2 prg-localcount2-base3:1.2 prg-localcount2-base2:1.2 prg-localcount2-base1:1.2 prg-localcount2:1.2.0.6 prg-localcount2-base:1.2 pgoyette-localcount-20170426:1.2 bouyer-socketcan-base1:1.2 pgoyette-localcount-20170320:1.2 bouyer-socketcan:1.2.0.4 bouyer-socketcan-base:1.2 pgoyette-localcount-20170107:1.2 pgoyette-localcount-20161104:1.2 localcount-20160914:1.2 pgoyette-localcount-20160806:1.2 pgoyette-localcount-20160726:1.2 pgoyette-localcount:1.2.0.2 pgoyette-localcount-base:1.2 tls-maxphys-base:1.2 yamt-pagecache:1.1.1.1.0.4 yamt-pagecache-base9:1.1.1.1 tls-earlyentropy:1.1.1.1.0.2 tls-earlyentropy-base:1.2 riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.1.1.1 riastradh-drm2-base3:1.1.1.1 bind-9-10-0b1:1.1.1.1 ISC:1.1.1; locks; strict; comment @# @; 1.2 date 2014.07.08.05.43.39; author spz; state dead; branches; next 1.1; commitid 38uNaLtUSZRtgxHx; 1.1 date 2014.02.28.17.40.12; author christos; state Exp; branches 1.1.1.1; next ; commitid F63APPkuuRyMpTqx; 1.1.1.1 date 2014.02.28.17.40.12; author christos; state Exp; branches 1.1.1.1.2.1 1.1.1.1.4.1; next ; commitid F63APPkuuRyMpTqx; 1.1.1.1.2.1 date 2014.08.10.07.06.41; author tls; state dead; branches; next ; commitid vuZWZSMzG2mZFMLx; 1.1.1.1.4.1 date 2014.02.28.17.40.12; author yamt; state dead; branches; next 1.1.1.1.4.2; commitid qlg4WCl9yarq6yBx; 1.1.1.1.4.2 date 2014.05.22.15.43.16; author yamt; state Exp; branches; next ; commitid qlg4WCl9yarq6yBx; desc @@ 1.2 log @merge for bind 9.10.0-P2, first go @ text @ delve
delve
Prev  Manual pages  Next

Name

delve — DNS lookup and validation utility

Synopsis

delve [@@server] [-4] [-6] [-a anchor-file] [-b address] [-c class] [-d level] [-i] [-m] [-p port#] [-q name] [-t type] [-x addr] [name] [type] [class] [queryopt...]

delve [-h]

delve [-v]

delve [queryopt...] [query...]

DESCRIPTION

delve (Domain Entity Lookup & Validation Engine) is a tool for sending DNS queries and validating the results, using the the same internal resolver and validator logic as named.

delve will send to a specified name server all queries needed to fetch and validate the requested data; this includes the original requested query, subsequent queries to follow CNAME or DNAME chains, and queries for DNSKEY, DS and DLV records to establish a chain of trust for DNSSEC validation. It does not perform iterative resolution, but simulates the behavior of a name server configured for DNSSEC validating and forwarding.

By default, responses are validated using built-in DNSSEC trust anchors for the root zone (".") and for the ISC DNSSEC lookaside validation zone ("dlv.isc.org"). Records returned by delve are either fully validated or were not signed. If validation fails, an explanation of the failure is included in the output; the validation process can be traced in detail. Because delve does not rely on an external server to carry out validation, it can be used to check the validity of DNS responses in environments where local name servers may not be trustworthy.

Unless it is told to query a specific name server, delve will try each of the servers listed in /etc/resolv.conf. If no usable server addresses are found, delve will send queries to the localhost addresses (127.0.0.1 for IPv4, ::1 for IPv6).

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

SIMPLE USAGE

A typical invocation of delve looks like: 

 delve @@server name type

where:

server

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 server argument is a hostname, delve resolves that name before querying that name server (note, however, that this initial lookup is not validated by DNSSEC).

If no server argument is provided, delve consults /etc/resolv.conf; if an address is found there, it queries the name server at that address. If either of the -4 or -6 options are in use, then only addresses for the corresponding transport will be tried. If no usable addresses are found, delve will send queries to the localhost addresses (127.0.0.1 for IPv4, ::1 for IPv6).

name

is the domain name to be looked up.

type

indicates what type of query is required — ANY, A, MX, etc. type can be any valid query type. If no type argument is supplied, delve will perform a lookup for an A record.

OPTIONS

-a anchor-file

Specifies a file from which to read DNSSEC trust anchors. The default is /etc/bind.keys, which is included with BIND 9 and contains trust anchors for the root zone (".") and for the ISC DNSSEC lookaside validation zone ("dlv.isc.org").

Keys that do not match the root or DLV trust-anchor names are ignored; these key names can be overridden using the +dlv=NAME or +root=NAME options.

Note: When reading the trust anchor file, delve treats managed-keys statements and trusted-keys statements identically. That is, for a managed key, it is the initial key that is trusted; RFC 5011 key management is not supported. delve will not consult the managed-keys database maintained by named. This means that if either of the keys in /etc/bind.keys is revoked and rolled over, it will be necessary to update /etc/bind.keys to use DNSSEC validation in delve.

-b address

Sets the source IP address of the query to address. This must be a valid address on one of the host's network interfaces or "0.0.0.0" or "::". An optional source port may be specified by appending "#<port>"

-c class

Sets the query class for the requested data. Currently, only class "IN" is supported in delve and any other value is ignored.

-d level

Set the systemwide debug level to level. The allowed range is from 0 to 99. The default is 0 (no debugging). Debugging traces from delve become more verbose as the debug level increases. See the +mtrace, +rtrace, and +vtrace options below for additional debugging details.

-h

Display the delve help usage output and exit.

-i

Insecure mode. This disables internal DNSSEC validation. (Note, however, this does not set the CD bit on upstream queries. If the server being queried is performing DNSSEC validation, then it will not return invalid data; this can cause delve to time out. When it is necessary to examine invalid data to debug a DNSSEC problem, use dig +cd.)

-m

Enables memory usage debugging.

-p port#

Specifies a destination port to use for queries instead of the standard DNS port number 53. This option would be used with a name server that has been configured to listen for queries on a non-standard port number.

-q name

Sets the query name to name. While the query name can be specified without using the -q, it is sometimes necessary to disambiguate names from types or classes (for example, when looking up the name "ns", which could be misinterpreted as the type NS, or "ch", which could be misinterpreted as class CH).

-t type

Sets the query type to type, which can be any valid query type supported in BIND 9 except for zone transfer types AXFR and IXFR. As with -q, this is useful to distinguish query name type or class when they are ambiguous. it is sometimes necessary to disambiguate names from types.

The default query type is "A", unless the -x option is supplied to indicate a reverse lookup, in which case it is "PTR".

-v

Print the delve version and exit.

-x addr

Performs a reverse lookup, mapping an addresses to a name. addr is an IPv4 address in dotted-decimal notation, or a colon-delimited IPv6 address. When -x is used, there is no need to provide the name or type arguments. delve automatically performs a lookup for a name like 11.12.13.10.in-addr.arpa and sets the query type to PTR. IPv6 addresses are looked up using nibble format under the IP6.ARPA domain.

-4

Forces delve to only use IPv4.

-6

Forces delve to only use IPv6.

QUERY OPTIONS

delve provides a number of query options which affect the way results are displayed, and in some cases the way lookups are performed.

Each query option is identified by a keyword preceded by a plus sign (+). Some keywords set or reset an option. These may be preceded by the string no to negate the meaning of that keyword. Other keywords assign values to options like the timeout interval. They have the form +keyword=value. The query options are:

+[no]cdflag

Controls whether to set the CD (checking disabled) bit in queries sent by delve. This may be useful when troubleshooting DNSSEC problems from behind a validating resolver. A validating resolver will block invalid responses, making it difficult to retrieve them for analysis. Setting the CD flag on queries will cause the resolver to return invalid responses, which delve can then validate internally and report the errors in detail.

+[no]class

Controls whether to display the CLASS when printing a record. The default is to display the CLASS.

+[no]ttl

Controls whether to display the TTL when printing a record. The default is to display the TTL.

+[no]rtrace

Toggle resolver fetch logging. This reports the name and type of each query sent by delve in the process of carrying out the resolution and validation process: this includes including the original query and all subsequent queries to follow CNAMEs and to establish a chain of trust for DNSSEC validation.

This is equivalent to setting the debug level to 1 in the "resolver" logging category. Setting the systemwide debug level to 1 using the -d option will product the same output (but will affect other logging categories as well).

+[no]mtrace

Toggle message logging. This produces a detailed dump of the responses received by delve in the process of carrying out the resolution and validation process.

This is equivalent to setting the debug level to 10 for the the "packets" module of the "resolver" logging category. Setting the systemwide debug level to 10 using the -d option will produce the same output (but will affect other logging categories as well).

+[no]vtrace

Toggle validation logging. This shows the internal process of the validator as it determines whether an answer is validly signed, unsigned, or invalid.

This is equivalent to setting the debug level to 3 for the the "validator" module of the "dnssec" logging category. Setting the systemwide debug level to 3 using the -d option will produce the same output (but will affect other logging categories as well).

+[no]short

Provide a terse answer. The default is to print the answer in a verbose form.

+[no]comments

Toggle the display of comment lines in the output. The default is to print comments.

+[no]rrcomments

Toggle the display of per-record comments in the output (for example, human-readable key information about DNSKEY records). The default is to print per-record comments.

+[no]crypto

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 ]".

+[no]trust

Controls whether to display the trust level when printing a record. The default is to display the trust level.

+[no]split[=W]

Split long hex- or base64-formatted fields in resource records into chunks of W characters (where W is rounded up to the nearest multiple of 4). +nosplit or +split=0 causes fields not to be split at all. The default is 56 characters, or 44 characters when multiline mode is active.

+[no]all

Set or clear the display options +[no]comments, +[no]rrcomments, and +[no]trust as a group.

+[no]multiline

Print long records (such as RRSIG, DNSKEY, and 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 delve output.

+[no]dnssec

Indicates whether to display RRSIG records in the delve output. The default is to do so. Note that (unlike in dig) this does not control whether to request DNSSEC records or whether to validate them. DNSSEC records are always requested, and validation will always occur unless suppressed by the use of -i or +noroot and +nodlv.

+[no]root[=ROOT]

Indicates whether to perform conventional (non-lookaside) DNSSEC validation, and if so, specifies the name of a trust anchor. The default is to validate using a trust anchor of "." (the root zone), for which there is a built-in key. If specifying a different trust anchor, then -a must be used to specify a file containing the key.

+[no]dlv[=DLV]

Indicates whether to perform DNSSEC lookaside validation, and if so, specifies the name of the DLV trust anchor. The default is to perform lookaside validation using a trust anchor of "dlv.isc.org", for which there is a built-in key. If specifying a different name, then -a must be used to specify a file containing the DLV key.

FILES

/etc/bind.keys

/etc/resolv.conf

SEE ALSO

dig(1), named(8), RFC4034, RFC4035, RFC4431, RFC5074, RFC5155.

Prev  Up  Next
host  Home  dnssec-checkds
@ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Introduction BIND 9.10.0b1 is the first beta development release of BIND 9.10, a new branch of BIND 9. This document summarizes features added or significantly changed since the previous major release, BIND 9.9. Items that were not in the previous development release, BIND 9.10.0a2, are marked with asterisks (**). Bug fixes since the previous development release are also summarized. Please see the CHANGES file in the source code release for a complete list of all changes. Download The latest versions of BIND 9 software can always be found on our web site at http://www.isc.org/downloads/. There you will find additional information about each release, source code, and pre-compiled versions for Microsoft Windows operating systems. Support Professional support is provided by Internet Systems Consortium, Inc., doing business as DNSco. Information about paid support options is available at http://www.dns-co.com/solutions/. Free support is provided by our user community via a mailing list. Information on all public email lists is available at https://www.isc.org/community/mailing-list/. New Features DNS Response-rate limiting (DNS RRL), which blunts the impact of reflection and amplification attacks, is always compiled in and no longer requires a compile-time option to enable it. An experimental "Source Identity Token" (SIT) EDNS option is now available. Similar to DNS Cookies (as invented by Donald Eastlake III and described in draft-eastlake-dnsext-cookies-04), these are designed to enable clients to detect off-path spoofed responses, and to enable servers to detect spoofed-source queries. Servers can be configured to send smaller responses to clients that have not identified themselves using a SIT option, reducing the effectiveness of amplification attacks. RRL processing has also been updated: clients proven to be legitimate via SIT are not subject to rate limiting. Use "configure --enable-sit" to enable this feature in BIND 9. [RT #35389] ** A new zone file format, "map", stores zone data in a format that can be mapped directly into memory, allowing significantly faster zone loading. [RT #25419] "delve" (domain entity lookup and validation engine) is a new tool with dig-like semantics for looking up DNS data and performing internal DNSSEC validation. This allows easy validation in environments where the resolver may not be trustworthy, and assists with troubleshooting of DNSSEC problems. (Note: not yet available on Windows.) [RT #32406] ** The new "prefetch" option can improve recursive resolver performance: when it is in use, cache records that are still being requested by clients will automatically be refreshed from the authoritative server before they expire, reducing or eliminating the time window in which no answer is available in the cache. [RT #35041] Improved EDNS processing allows better resolver performance and reliability over slow or lossy connections. [RT #30655] Substantial improvements have been made in response-policy zone (RPZ) performance. Up to 32 response-policy zones can now be configured. Performance loss due to adding additional RPZs is minimal. RPZ now allows response policies to be configured based on the IP address of the client. ACLs can now be specified based on geographic location using the MaxMind GeoIP databases. Use "configure --with-geoip" to enable this feature in BIND 9. Thanks to Ken Brownfield for the contribution. [RT #30681] The version 3 XML schema for the statistics channel, including new statistics and a flattened XML tree for faster parsing, is no longer optional. The version 2 XML schema is now deprecated. [RT #30023] Improvements have been made to the XSL stylesheet used for XML statistics: The stylesheet can now be cached by the browser; section headers are omitted when the sections have no data to display; counter readability has been improved. Also, broken-out subgroups of XML statistics (server, zones, net, tasks, mem, and status) can now be requested. Thanks to Timothe Litt for the assistance. [RT #35115] [RT #35117] The statistics channel can now provide data in JSON format as well as XML. Per-zone stats counters have been added to track TCP and UDP queries. [RT #35375] ** Server-wide stats counters have been added to track EDNS options received. [RT #35447] ** The new "in-view" zone option allows zone data to be shared between views, so that multiple views can serve the same zones authoritatively without storing multiple copies in memory. [RT #32968] A new compile-time option, "configure --enable-native-pkcs11", allows the BIND 9 cryptography functions to use the PKCS#11 API natively, so that BIND can drive a cryptographic hardware service module (HSM) directly instead of using a modified OpenSSL as an intermediary. This has been tested with the Thales nShield HSM and with SoftHSMv2 from the OpenDNSSEC project. [RT #29031] When re-signing a zone, the new "dnssec-signzone -Q" option drops signatures from keys that are still published but are no longer active. Thanks to Pierre Beyssac for the contribution. [RT #34990] New options have been added to "dnssec-coverage": -z and -k indicate whether to limit coverage checks to ZSK's or KSK's, and -l limits coverage checking to a specified duration. Thanks to Peter Palfrader for the contribution. [RT #35168] "named-checkconf -px" will print the contents of configuration files with the shared secrets obscured, making it easier to share configuration (e.g. when submitting a bug report) without revealing private information. [RT #34465] Added a "no-case-compress" ACL, which causes "named" to use case-insensitive compression for specified clients. This is useful when dealing with broken client implementations that use case-sensitive name comparisons, rejecting responses that fail to match the capitalization of the query that was sent. "named" now preserves the capitalization of names when responding to queries: for instance, a query for "example.com" may be answered with "example.COM" if the name was configured that way in the zone file. Some clients have a bug causing them to depend on the older behavior, in which the case of the answer always matched the case of the query, rather than the case of the name configured in the DNS. Such clients can now be specified in the new "no-case-compress" ACL; this will restore the older behavior of "named" for those clients only. [RT #35300] ** On operating systems that support routing sockets, including Mac OSX, *BSD and Linux, network interfaces are re-scanned automatically whenever they change. Use "automatic-interface-scan no;" to disable this feature. [RT #23027] ** Added "rndc scan" to trigger an interface scan manually. [RT #23027] ** A new compile-time option, "configure --with-tuning=3Dlarge", tunes various compiled-in constants and default settings to values suited to large servers with abundant memory. This can improve performance on such servers, but will consume more memory and may degrade performance on smaller systems. [RT #29538] ** The new "max-zone-ttl" option enforces maximum TTLs for zones. If loading a zone containing a higher TTL, the load fails. DDNS updates with higher TTLs are accepted but the TTL is truncated. (Note: Currently supported for master zones only; inline-signing slaves will be added.) [RT #38405] ** Added a new "dig +subnet" option to send an EDNS CLIENT-SUBNET option (as described in draft-vandergaast-edns-client-subnet-02) containing the specified address/prefix when querying. Thanks to Wilmer van der Gaast for the contribution. [RT #35415] ** Partially implemented the EDNS EXPIRE option (as described in draft-andrews-dnsext-expire-00). "dig +expire" sends an EXPIRE option when querying. When this option is sent with an SOA query to a slave zone running on a server that supports the option, the response will report the time until the slave zone expires. EXPIRE uses an experimental option code (65002), which is subject to change when a permanent code is assigned by IANA. [RT #35416] ** Multiple DLZ databases can now be configured, and are searched in order to find one that can answer an incoming query. Individual zones can now be configured to be served from a specific DLZ database. DLZ databases can serve zones of type "master" and "redirect". "named-checkzone" and "named-compilezone" can now read journal files, allowing them to process dynamic zones without the zones needing to be frozen first. The "rndc" command now supports new key algorithms in addition to HMAC-MD5, including HMAC-SHA1, -SHA224, -SHA256, -SHA384, and -SHA512. The -A option to rndc-confgen can be used to select the algorithm for the generated key. (The default is still HMAC-MD5; this may change in a future release.) [RT #20363] The internal and export versions of the BIND libraries (libisc, libdns, etc) have been unified so that external library clients can use the same libraries as BIND itself. [RT #33131] Added a "Configure" script for Windows to simplify enabling or disabling optional features. All versions of Visual Studio up to 2013 are now supported, and support has been added for 64-bit builds. Zip files containing pre-compiled 64-bit versions of BIND 9 are now included with releases. [RT #34160] ** "rndc zonestatus" reports information about a specified zone. "named" now listens on IPv6 as well as IPv4 interfaces by default. Feature Changes The default setting for the -U option (setting the number of UDP listeners per interface) has been adjusted to improve performance. [RT #35417] ** Updated zkt and nslint in the contrib directory to the newest versions: zkt 1.1.2 and nslint-3.0a2. ** The isc_bitstring API is no longer used and has been removed from the libisc library. [RT #35284] ** The word "never" can now be used as a synonym for "none" when configuring key event dates in the dnssec tools. [RT #35277] ** The new libiscpk11 library, introduced in the previous development release to support native PKCS#11, has been merged into libisc to simplify dependencies. [RT #35205] ** Documentation of native PKCS#11 has been expanded, specifically to describe the new pkcs11: URI format used in key labels. [RT #35287] *= * The Windows installer now places files in the Program Files area rather than system services. [RT #35361] ** The timestamps included in RRSIG records can now be read as integers indicating the number of seconds since the UNIX epoch, in addition to being read as formatted dates in YYYYMMDDHHMMSS format. [RT #35185] The irs_resconf_load() function, used for reading /etc/resolv.conf, now returns ISC_R_FILENOTFOUND when the file is missing or unreadable. However, it will still initialize an irs_resconf structure as if the file had been configured with nameservers at the IPv4 and IPv6 localhost addresses. Existing code that uses irs_resconf_load() will need to be updated to treat ISC_R_FILENOTFOUND as a qualified success, or it may leak memory due to treating the result as a failure even though an irs_resconf structure was allocated; see CHANGES for sample C code that implements the correct behavior [RT #35194] Bug Fixes "dnssec-keygen" could set the publication date incorrectly when only the activation date was specified on the command line. [RT #35278] Fixed a type mismatch causing the ODBC DLZ driver to dump core on 64-bit systems. [RT #35324] Improved building with libtool. [RT #35314] When a server is specified by name in "nsupdate", all addresses for that name will be tried before giving up. Previously, if the first address for the server name was not reachable the update would fail. [RT #25784] Fixed an assertion failure caused by using "rndc retransfer" with inline-signing zones. [RT #35353] Fixed a build failure from using "./configure --enable-openssl-hash". [RT #35343] The "delegation-only" flag now works in zones of type "forward". (This had previously been documented to work, but this was actually rejected by the configuration parser.) [RT #35392] Fixed a race condition which could lead to a core dump when destroying a resolver fetch object. [RT #35385] Addressed a potential REQUIRE failure that could occur when printing out an rdataset using a format that includes comment data. The "allow-notify" ACL formerly ignored TSIG keys; this has been corrected. [RT #35425] Fixed an uninitialized pointer in log.c that could potentially have caused a core dump on some platforms. [RT #35260] Thank You Thank you to everyone who assisted us in making this release possible. If you would like to contribute to ISC to assist us in continuing to make quality open source software, please visit our donations page at http://www.isc.org/donate/. (c) 2001-2014 Internet Systems Consortium @ text @@ 1.1.1.1.2.1 log @Rebase. @ text @@ 1.1.1.1.4.1 log @file man.delve.html was added on branch yamt-pagecache on 2014-05-22 15:43:16 +0000 @ text @d1 503 @ 1.1.1.1.4.2 log @sync with head. for a reference, the tree before this commit was tagged as yamt-pagecache-tag8. this commit was splitted into small chunks to avoid a limitation of cvs. ("Protocol error: too many arguments") @ text @a0 503 delve
delve
Prev  Manual pages  Next

Name

delve — DNS lookup and validation utility

Synopsis

delve [@@server] [-4] [-6] [-a anchor-file] [-b address] [-c class] [-d level] [-i] [-m] [-p port#] [-q name] [-t type] [-x addr] [name] [type] [class] [queryopt...]

delve [-h]

delve [-v]

delve [queryopt...] [query...]

DESCRIPTION

delve (Domain Entity Lookup & Validation Engine) is a tool for sending DNS queries and validating the results, using the the same internal resolver and validator logic as named.

delve will send to a specified name server all queries needed to fetch and validate the requested data; this includes the original requested query, subsequent queries to follow CNAME or DNAME chains, and queries for DNSKEY, DS and DLV records to establish a chain of trust for DNSSEC validation. It does not perform iterative resolution, but simulates the behavior of a name server configured for DNSSEC validating and forwarding.

By default, responses are validated using built-in DNSSEC trust anchors for the root zone (".") and for the ISC DNSSEC lookaside validation zone ("dlv.isc.org"). Records returned by delve are either fully validated or were not signed. If validation fails, an explanation of the failure is included in the output; the validation process can be traced in detail. Because delve does not rely on an external server to carry out validation, it can be used to check the validity of DNS responses in environments where local name servers may not be trustworthy.

Unless it is told to query a specific name server, delve will try each of the servers listed in /etc/resolv.conf. If no usable server addresses are found, delve will send queries to the localhost addresses (127.0.0.1 for IPv4, ::1 for IPv6).

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

SIMPLE USAGE

A typical invocation of delve looks like: 

 delve @@server name type

where:

server

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 server argument is a hostname, delve resolves that name before querying that name server (note, however, that this initial lookup is not validated by DNSSEC).

If no server argument is provided, delve consults /etc/resolv.conf; if an address is found there, it queries the name server at that address. If either of the -4 or -6 options are in use, then only addresses for the corresponding transport will be tried. If no usable addresses are found, delve will send queries to the localhost addresses (127.0.0.1 for IPv4, ::1 for IPv6).

name

is the domain name to be looked up.

type

indicates what type of query is required — ANY, A, MX, etc. type can be any valid query type. If no type argument is supplied, delve will perform a lookup for an A record.

OPTIONS

-a anchor-file

Specifies a file from which to read DNSSEC trust anchors. The default is /etc/bind.keys, which is included with BIND 9 and contains trust anchors for the root zone (".") and for the ISC DNSSEC lookaside validation zone ("dlv.isc.org").

Keys that do not match the root or DLV trust-anchor names are ignored; these key names can be overridden using the +dlv=NAME or +root=NAME options.

Note: When reading the trust anchor file, delve treats managed-keys statements and trusted-keys statements identically. That is, for a managed key, it is the initial key that is trusted; RFC 5011 key management is not supported. delve will not consult the managed-keys database maintained by named. This means that if either of the keys in /etc/bind.keys is revoked and rolled over, it will be necessary to update /etc/bind.keys to use DNSSEC validation in delve.

-b address

Sets the source IP address of the query to address. This must be a valid address on one of the host's network interfaces or "0.0.0.0" or "::". An optional source port may be specified by appending "#<port>"

-c class

Sets the query class for the requested data. Currently, only class "IN" is supported in delve and any other value is ignored.

-d level

Set the systemwide debug level to level. The allowed range is from 0 to 99. The default is 0 (no debugging). Debugging traces from delve become more verbose as the debug level increases. See the +mtrace, +rtrace, and +vtrace options below for additional debugging details.

-h

Display the delve help usage output and exit.

-i

Insecure mode. This disables internal DNSSEC validation. (Note, however, this does not set the CD bit on upstream queries. If the server being queried is performing DNSSEC validation, then it will not return invalid data; this can cause delve to time out. When it is necessary to examine invalid data to debug a DNSSEC problem, use dig +cd.)

-m

Enables memory usage debugging.

-p port#

Specifies a destination port to use for queries instead of the standard DNS port number 53. This option would be used with a name server that has been configured to listen for queries on a non-standard port number.

-q name

Sets the query name to name. While the query name can be specified without using the -q, it is sometimes necessary to disambiguate names from types or classes (for example, when looking up the name "ns", which could be misinterpreted as the type NS, or "ch", which could be misinterpreted as class CH).

-t type

Sets the query type to type, which can be any valid query type supported in BIND 9 except for zone transfer types AXFR and IXFR. As with -q, this is useful to distinguish query name type or class when they are ambiguous. it is sometimes necessary to disambiguate names from types.

The default query type is "A", unless the -x option is supplied to indicate a reverse lookup, in which case it is "PTR".

-v

Print the delve version and exit.

-x addr

Performs a reverse lookup, mapping an addresses to a name. addr is an IPv4 address in dotted-decimal notation, or a colon-delimited IPv6 address. When -x is used, there is no need to provide the name or type arguments. delve automatically performs a lookup for a name like 11.12.13.10.in-addr.arpa and sets the query type to PTR. IPv6 addresses are looked up using nibble format under the IP6.ARPA domain.

-4

Forces delve to only use IPv4.

-6

Forces delve to only use IPv6.

QUERY OPTIONS

delve provides a number of query options which affect the way results are displayed, and in some cases the way lookups are performed.

Each query option is identified by a keyword preceded by a plus sign (+). Some keywords set or reset an option. These may be preceded by the string no to negate the meaning of that keyword. Other keywords assign values to options like the timeout interval. They have the form +keyword=value. The query options are:

+[no]cdflag

Controls whether to set the CD (checking disabled) bit in queries sent by delve. This may be useful when troubleshooting DNSSEC problems from behind a validating resolver. A validating resolver will block invalid responses, making it difficult to retrieve them for analysis. Setting the CD flag on queries will cause the resolver to return invalid responses, which delve can then validate internally and report the errors in detail.

+[no]class

Controls whether to display the CLASS when printing a record. The default is to display the CLASS.

+[no]ttl

Controls whether to display the TTL when printing a record. The default is to display the TTL.

+[no]rtrace

Toggle resolver fetch logging. This reports the name and type of each query sent by delve in the process of carrying out the resolution and validation process: this includes including the original query and all subsequent queries to follow CNAMEs and to establish a chain of trust for DNSSEC validation.

This is equivalent to setting the debug level to 1 in the "resolver" logging category. Setting the systemwide debug level to 1 using the -d option will product the same output (but will affect other logging categories as well).

+[no]mtrace

Toggle message logging. This produces a detailed dump of the responses received by delve in the process of carrying out the resolution and validation process.

This is equivalent to setting the debug level to 10 for the the "packets" module of the "resolver" logging category. Setting the systemwide debug level to 10 using the -d option will produce the same output (but will affect other logging categories as well).

+[no]vtrace

Toggle validation logging. This shows the internal process of the validator as it determines whether an answer is validly signed, unsigned, or invalid.

This is equivalent to setting the debug level to 3 for the the "validator" module of the "dnssec" logging category. Setting the systemwide debug level to 3 using the -d option will produce the same output (but will affect other logging categories as well).

+[no]short

Provide a terse answer. The default is to print the answer in a verbose form.

+[no]comments

Toggle the display of comment lines in the output. The default is to print comments.

+[no]rrcomments

Toggle the display of per-record comments in the output (for example, human-readable key information about DNSKEY records). The default is to print per-record comments.

+[no]crypto

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 ]".

+[no]trust

Controls whether to display the trust level when printing a record. The default is to display the trust level.

+[no]split[=W]

Split long hex- or base64-formatted fields in resource records into chunks of W characters (where W is rounded up to the nearest multiple of 4). +nosplit or +split=0 causes fields not to be split at all. The default is 56 characters, or 44 characters when multiline mode is active.

+[no]all

Set or clear the display options +[no]comments, +[no]rrcomments, and +[no]trust as a group.

+[no]multiline

Print long records (such as RRSIG, DNSKEY, and 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 delve output.

+[no]dnssec

Indicates whether to display RRSIG records in the delve output. The default is to do so. Note that (unlike in dig) this does not control whether to request DNSSEC records or whether to validate them. DNSSEC records are always requested, and validation will always occur unless suppressed by the use of -i or +noroot and +nodlv.

+[no]root[=ROOT]

Indicates whether to perform conventional (non-lookaside) DNSSEC validation, and if so, specifies the name of a trust anchor. The default is to validate using a trust anchor of "." (the root zone), for which there is a built-in key. If specifying a different trust anchor, then -a must be used to specify a file containing the key.

+[no]dlv[=DLV]

Indicates whether to perform DNSSEC lookaside validation, and if so, specifies the name of the DLV trust anchor. The default is to perform lookaside validation using a trust anchor of "dlv.isc.org", for which there is a built-in key. If specifying a different name, then -a must be used to specify a file containing the DLV key.

FILES

/etc/bind.keys

/etc/resolv.conf

SEE ALSO

dig(1), named(8), RFC4034, RFC4035, RFC4431, RFC5074, RFC5155.

Prev  Up  Next
host  Home  dnssec-checkds
@