1NAMED-CHECKZONE(8) BIND9 NAMED-CHECKZONE(8)
2
6 named-checkzone, named-compilezone - zone file validity checking or
7 converting tool
8
10 named-checkzone [-d] [-h] [-j] [-q] [-v] [-c class] [-f format]
11 [-F format] [-J filename] [-i mode] [-k mode] [-m mode]
12 [-M mode] [-n mode] [-l ttl] [-L serial] [-o filename]
13 [-r mode] [-s style] [-S mode] [-t directory] [-T mode]
14 [-w directory] [-D] [-W mode] {zonename} {filename}
15 named-compilezone [-d] [-j] [-q] [-v] [-c class] [-C mode] [-f format]
17 [-F format] [-J filename] [-i mode] [-k mode]
18 [-m mode] [-n mode] [-l ttl] [-L serial] [-r mode]
19 [-s style] [-t directory] [-T mode] [-w directory]
20 [-D] [-W mode] {-o filename} {zonename} {filename}
21
23 named-checkzone checks the syntax and integrity of a zone file. It
24 performs the same checks as named does when loading a zone. This makes
25 named-checkzone useful for checking zone files before configuring them
26 into a name server.
27 named-compilezone is similar to named-checkzone, but it always dumps
29 the zone contents to a specified file in a specified format.
30 Additionally, it applies stricter check levels by default, since the
31 dump output will be used as an actual zone file loaded by named. When
32 manually specified otherwise, the check levels must at least be as
33 strict as those specified in the named configuration file.
34
36 -d
37 Enable debugging.
38 -h
40 Print the usage summary and exit.
41 -q
43 Quiet mode - exit code only.
44 -v
46 Print the version of the named-checkzone program and exit.
47 -j
49 When loading a zone file, read the journal if it exists. The
50 journal file name is assumed to be the zone file name appended with
51 the string .jnl.
52 -J filename
54 When loading the zone file read the journal from the given file, if
55 it exists. (Implies -j.)
56 -c class
58 Specify the class of the zone. If not specified, "IN" is assumed.
59 -i mode
61 Perform post-load zone integrity checks. Possible modes are "full"
62 (default), "full-sibling", "local", "local-sibling" and "none".
63 Mode "full" checks that MX records refer to A or AAAA record (both
65 in-zone and out-of-zone hostnames). Mode "local" only checks MX
66 records which refer to in-zone hostnames.
67 Mode "full" checks that SRV records refer to A or AAAA record (both
69 in-zone and out-of-zone hostnames). Mode "local" only checks SRV
70 records which refer to in-zone hostnames.
71 Mode "full" checks that delegation NS records refer to A or AAAA
73 record (both in-zone and out-of-zone hostnames). It also checks
74 that glue address records in the zone match those advertised by the
75 child. Mode "local" only checks NS records which refer to in-zone
76 hostnames or that some required glue exists, that is when the
77 nameserver is in a child zone.
78 Mode "full-sibling" and "local-sibling" disable sibling glue checks
80 but are otherwise the same as "full" and "local" respectively.
81 Mode "none" disables the checks.
83 -f format
85 Specify the format of the zone file. Possible formats are "text"
86 (default), "raw", and "map".
87 -F format
89 Specify the format of the output file specified. For
90 named-checkzone, this does not cause any effects unless it dumps
91 the zone contents.
92 Possible formats are "text" (default), which is the standard
94 textual representation of the zone, and "map", "raw", and "raw=N",
95 which store the zone in a binary format for rapid loading by named.
96 "raw=N" specifies the format version of the raw zone file: if N is
97 0, the raw file can be read by any version of named; if N is 1, the
98 file can be read by release 9.9.0 or higher; the default is 1.
99 -k mode
101 Perform "check-names" checks with the specified failure mode.
102 Possible modes are "fail" (default for named-compilezone), "warn"
103 (default for named-checkzone) and "ignore".
104 -l ttl
106 Sets a maximum permissible TTL for the input file. Any record with
107 a TTL higher than this value will cause the zone to be rejected.
108 This is similar to using the max-zone-ttl option in named.conf.
109 -L serial
111 When compiling a zone to "raw" or "map" format, set the "source
112 serial" value in the header to the specified serial number. (This
113 is expected to be used primarily for testing purposes.)
114 -m mode
116 Specify whether MX records should be checked to see if they are
117 addresses. Possible modes are "fail", "warn" (default) and
118 "ignore".
119 -M mode
121 Check if a MX record refers to a CNAME. Possible modes are "fail",
122 "warn" (default) and "ignore".
123 -n mode
125 Specify whether NS records should be checked to see if they are
126 addresses. Possible modes are "fail" (default for
127 named-compilezone), "warn" (default for named-checkzone) and
128 "ignore".
129 -o filename
131 Write zone output to filename. If filename is - then write to
132 standard out. This is mandatory for named-compilezone.
133 -r mode
135 Check for records that are treated as different by DNSSEC but are
136 semantically equal in plain DNS. Possible modes are "fail", "warn"
137 (default) and "ignore".
138 -s style
140 Specify the style of the dumped zone file. Possible styles are
141 "full" (default) and "relative". The full format is most suitable
142 for processing automatically by a separate script. On the other
143 hand, the relative format is more human-readable and is thus
144 suitable for editing by hand. For named-checkzone this does not
145 cause any effects unless it dumps the zone contents. It also does
146 not have any meaning if the output format is not text.
147 -S mode
149 Check if a SRV record refers to a CNAME. Possible modes are "fail",
150 "warn" (default) and "ignore".
151 -t directory
153 Chroot to directory so that include directives in the configuration
154 file are processed as if run by a similarly chrooted named.
155 -T mode
157 Check if Sender Policy Framework (SPF) records exist and issues a
158 warning if an SPF-formatted TXT record is not also present.
159 Possible modes are "warn" (default), "ignore".
160 -w directory
162 chdir to directory so that relative filenames in master file
163 $INCLUDE directives work. This is similar to the directory clause
164 in named.conf.
165 -D
167 Dump zone file in canonical format. This is always enabled for
168 named-compilezone.
169 -W mode
171 Specify whether to check for non-terminal wildcards. Non-terminal
172 wildcards are almost always the result of a failure to understand
173 the wildcard matching algorithm (RFC 1034). Possible modes are
174 "warn" (default) and "ignore".
175 zonename
177 The domain name of the zone being checked.
178 filename
180 The name of the zone file.
181
183 named-checkzone returns an exit status of 1 if errors were detected and
184 0 otherwise.
185
187 named(8), named-checkconf(8), RFC 1035, BIND 9 Administrator Reference
188 Manual.
189
191 Internet Systems Consortium, Inc.
192
194 Copyright © 2000-2002, 2004-2007, 2009-2016, 2018 Internet Systems
195 Consortium, Inc. ("ISC")
196ISC 2014-02-19 NAMED-CHECKZONE(8)