1NAMED-CHECKZONE(1) BIND 9 NAMED-CHECKZONE(1)
2
6 named-checkzone - zone file validity checking or converting tool
7
9 named-checkzone [-d] [-h] [-j] [-q] [-v] [-c class] [-C mode] [-f for‐
10 mat] [-F format] [-J filename] [-i mode] [-k mode] [-m mode] [-M mode]
11 [-n mode] [-l ttl] [-L serial] [-o filename] [-r mode] [-s style] [-S
12 mode] [-t directory] [-T mode] [-w directory] [-D] [-W mode] {zonename}
13 {filename}
14
16 named-checkzone checks the syntax and integrity of a zone file. It per‐
17 forms the same checks as named does when loading a zone. This makes
18 named-checkzone useful for checking zone files before configuring them
19 into a name server.
20
22 -d This option enables debugging.
23 -h This option prints the usage summary and exits.
25 -q This option sets quiet mode, which only sets an exit code to in‐
27 dicate successful or failed completion.
28 -v This option prints the version of the named-checkzone program
30 and exits.
31 -j When loading a zone file, this option tells named to read the
33 journal if it exists. The journal file name is assumed to be the
34 zone file name with the string .jnl appended.
35 -J filename
37 When loading the zone file, this option tells named to read the
38 journal from the given file, if it exists. This implies -j.
39 -c class
41 This option specifies the class of the zone. If not specified,
42 IN is assumed.
43 -C mode
45 This option controls check mode on zone files when loading.
46 Possible modes are check-svcb:fail and check-svcb:ignore.
47 check-svcb:fail turns on additional checks on _dns SVCB records
49 and check-svcb:ignore disables these checks. The default is
50 check-svcb:fail.
51 -i mode
53 This option performs post-load zone integrity checks. Possible
54 modes are full (the default), full-sibling, local, local-sib‐
55 ling, and none.
56 Mode full checks that MX records refer to A or AAAA records
58 (both in-zone and out-of-zone hostnames). Mode local only checks
59 MX records which refer to in-zone hostnames.
60 Mode full checks that SRV records refer to A or AAAA records
62 (both in-zone and out-of-zone hostnames). Mode local only checks
63 SRV records which refer to in-zone hostnames.
64 Mode full checks that delegation NS records refer to A or AAAA
66 records (both in-zone and out-of-zone hostnames). It also checks
67 that glue address records in the zone match those advertised by
68 the child. Mode local only checks NS records which refer to
69 in-zone hostnames or verifies that some required glue exists,
70 i.e., when the name server is in a child zone.
71 Modes full-sibling and local-sibling disable sibling glue
73 checks, but are otherwise the same as full and local, respec‐
74 tively.
75 Mode none disables the checks.
77 -f format
79 This option specifies the format of the zone file. Possible for‐
80 mats are text (the default), and raw.
81 -F format
83 This option specifies the format of the output file specified.
84 For named-checkzone, this does not have any effect unless it
85 dumps the zone contents.
86 Possible formats are text (the default), which is the standard
88 textual representation of the zone, and raw and raw=N, which
89 store the zone in a binary format for rapid loading by named.
90 raw=N specifies the format version of the raw zone file: if N is
91 0, the raw file can be read by any version of named; if N is 1,
92 the file can only be read by release 9.9.0 or higher. The de‐
93 fault is 1.
94 -k mode
96 This option performs check-names checks with the specified fail‐
97 ure mode. Possible modes are fail, warn (the default), and ig‐
98 nore.
99 -l ttl This option sets a maximum permissible TTL for the input file.
101 Any record with a TTL higher than this value causes the zone to
102 be rejected. This is similar to using the max-zone-ttl option in
103 named.conf.
104 -L serial
106 When compiling a zone to raw format, this option sets the
107 "source serial" value in the header to the specified serial num‐
108 ber. This is expected to be used primarily for testing purposes.
109 -m mode
111 This option specifies whether MX records should be checked to
112 see if they are addresses. Possible modes are fail, warn (the
113 default), and ignore.
114 -M mode
116 This option checks whether a MX record refers to a CNAME. Possi‐
117 ble modes are fail, warn (the default), and ignore.
118 -n mode
120 This option specifies whether NS records should be checked to
121 see if they are addresses. Possible modes are fail, warn (the
122 default), and ignore.
123 -o filename
125 This option writes the zone output to filename. If filename is
126 -, then the zone output is written to standard output.
127 -r mode
129 This option checks for records that are treated as different by
130 DNSSEC but are semantically equal in plain DNS. Possible modes
131 are fail, warn (the default), and ignore.
132 -s style
134 This option specifies the style of the dumped zone file. Possi‐
135 ble styles are full (the default) and relative. The full format
136 is most suitable for processing automatically by a separate
137 script. The relative format is more human-readable and is thus
138 suitable for editing by hand. This does not have any effect un‐
139 less it dumps the zone contents. It also does not have any mean‐
140 ing if the output format is not text.
141 -S mode
143 This option checks whether an SRV record refers to a CNAME. Pos‐
144 sible modes are fail, warn (the default), and ignore.
145 -t directory
147 This option tells named to chroot to directory, so that include
148 directives in the configuration file are processed as if run by
149 a similarly chrooted named.
150 -T mode
152 This option checks whether Sender Policy Framework (SPF) records
153 exist and issues a warning if an SPF-formatted TXT record is not
154 also present. Possible modes are warn (the default) and ignore.
155 -w directory
157 This option instructs named to chdir to directory, so that rela‐
158 tive filenames in master file $INCLUDE directives work. This is
159 similar to the directory clause in named.conf.
160 -D This option dumps the zone file in canonical format.
162 -W mode
164 This option specifies whether to check for non-terminal wild‐
165 cards. Non-terminal wildcards are almost always the result of a
166 failure to understand the wildcard matching algorithm (RFC
167 4592). Possible modes are warn (the default) and ignore.
168 zonename
170 This indicates the domain name of the zone being checked.
171 filename
173 This is the name of the zone file.
174
176 named-checkzone returns an exit status of 1 if errors were detected and
177 0 otherwise.
178
180 named(8), named-checkconf(8), named-compilezone(8), RFC 1035, BIND 9
181 Administrator Reference Manual.
182
184 Internet Systems Consortium
185
187 2023, Internet Systems Consortium
1889.19.18 NAMED-CHECKZONE(1)