1DNSSEC-VERIFY(8)                     BIND9                    DNSSEC-VERIFY(8)
2
3
4

NAME

6       dnssec-verify - DNSSEC zone verification tool
7

SYNOPSIS

9       dnssec-verify [-c class] [-E engine] [-I input-format] [-o origin]
10                     [-v level] [-V] [-x] [-z] {zonefile}
11

DESCRIPTION

13       dnssec-verify verifies that a zone is fully signed for each algorithm
14       found in the DNSKEY RRset for the zone, and that the NSEC / NSEC3
15       chains are complete.
16

OPTIONS

18       -c class
19           Specifies the DNS class of the zone.
20
21       -E engine
22           Specifies the cryptographic hardware to use, when applicable.
23
24           When BIND is built with OpenSSL PKCS#11 support, this defaults to
25           the string "pkcs11", which identifies an OpenSSL engine that can
26           drive a cryptographic accelerator or hardware service module. When
27           BIND is built with native PKCS#11 cryptography
28           (--enable-native-pkcs11), it defaults to the path of the PKCS#11
29           provider library specified via "--with-pkcs11".
30
31       -I input-format
32           The format of the input zone file. Possible formats are "text"
33           (default) and "raw". This option is primarily intended to be used
34           for dynamic signed zones so that the dumped zone file in a non-text
35           format containing updates can be verified independently. The use of
36           this option does not make much sense for non-dynamic zones.
37
38       -o origin
39           The zone origin. If not specified, the name of the zone file is
40           assumed to be the origin.
41
42       -v level
43           Sets the debugging level.
44
45       -V
46           Prints version information.
47
48       -x
49           Only verify that the DNSKEY RRset is signed with key-signing keys.
50           Without this flag, it is assumed that the DNSKEY RRset will be
51           signed by all active keys. When this flag is set, it will not be an
52           error if the DNSKEY RRset is not signed by zone-signing keys. This
53           corresponds to the -x option in dnssec-signzone.
54
55       -z
56           Ignore the KSK flag on the keys when determining whether the zone
57           if correctly signed. Without this flag it is assumed that there
58           will be a non-revoked, self-signed DNSKEY with the KSK flag set for
59           each algorithm and that RRsets other than DNSKEY RRset will be
60           signed with a different DNSKEY without the KSK flag set.
61
62           With this flag set, we only require that for each algorithm, there
63           will be at least one non-revoked, self-signed DNSKEY, regardless of
64           the KSK flag state, and that other RRsets will be signed by a
65           non-revoked key for the same algorithm that includes the
66           self-signed key; the same key may be used for both purposes. This
67           corresponds to the -z option in dnssec-signzone.
68
69       zonefile
70           The file containing the zone to be signed.
71

SEE ALSO

73       dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 4033.
74

AUTHOR

76       Internet Systems Consortium, Inc.
77

79       Copyright © 2012, 2014-2016, 2018-2021 Internet Systems Consortium,
80       Inc. ("ISC")
81
82
83
84ISC                               2014-01-15                  DNSSEC-VERIFY(8)
Impressum