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] [-i mode] [-k mode] [-m mode] [-M mode]
12 [-n mode] [-r mode] [-s style] [-S mode] [-t directory]
13 [-w directory] [-D] [-W mode] {zonename} {filename}
14 named-compilezone [-d] [-j] [-q] [-v] [-c class] [-C mode] [-f format]
16 [-F format] [-i mode] [-k mode] [-m mode] [-n mode]
17 [-o filename] [-r mode] [-s style] [-t directory]
18 [-w directory] [-D] [-W mode] {-o filename}
19 {zonename} {filename}
20
22 named-checkzone checks the syntax and integrity of a zone file. It
23 performs the same checks as named does when loading a zone. This makes
24 named-checkzone useful for checking zone files before configuring them
25 into a name server.
26 named-compilezone is similar to named-checkzone, but it always dumps
28 the zone contents to a specified file in a specified format.
29 Additionally, it applies stricter check levels by default, since the
30 dump output will be used as an actual zone file loaded by named. When
31 manually specified otherwise, the check levels must at least be as
32 strict as those specified in the named configuration file.
33
35 -d
36 Enable debugging.
37 -h
39 Print the usage summary and exit.
40 -q
42 Quiet mode - exit code only.
43 -v
45 Print the version of the named-checkzone program and exit.
46 -j
48 When loading the zone file read the journal if it exists.
49 -c class
51 Specify the class of the zone. If not specified, "IN" is assumed.
52 -i mode
54 Perform post-load zone integrity checks. Possible modes are "full"
55 (default), "full-sibling", "local", "local-sibling" and "none".
56 Mode "full" checks that MX records refer to A or AAAA record (both
58 in-zone and out-of-zone hostnames). Mode "local" only checks MX
59 records which refer to in-zone hostnames.
60 Mode "full" checks that SRV records refer to A or AAAA record (both
62 in-zone and out-of-zone hostnames). Mode "local" only checks SRV
63 records which refer to in-zone hostnames.
64 Mode "full" checks that delegation NS records refer to A or AAAA
66 record (both in-zone and out-of-zone hostnames). It also checks
67 that glue address records in the zone match those advertised by the
68 child. Mode "local" only checks NS records which refer to in-zone
69 hostnames or that some required glue exists, that is when the
70 nameserver is in a child zone.
71 Mode "full-sibling" and "local-sibling" disable sibling glue checks
73 but are otherwise the same as "full" and "local" respectively.
74 Mode "none" disables the checks.
76 -f format
78 Specify the format of the zone file. Possible formats are "text"
79 (default) and "raw".
80 -F format
82 Specify the format of the output file specified. Possible formats
83 are "text" (default) and "raw". For named-checkzone, this does not
84 cause any effects unless it dumps the zone contents.
85 -k mode
87 Perform "check-names" checks with the specified failure mode.
88 Possible modes are "fail" (default for named-compilezone), "warn"
89 (default for named-checkzone) and "ignore".
90 -m mode
92 Specify whether MX records should be checked to see if they are
93 addresses. Possible modes are "fail", "warn" (default) and
94 "ignore".
95 -M mode
97 Check if a MX record refers to a CNAME. Possible modes are "fail",
98 "warn" (default) and "ignore".
99 -n mode
101 Specify whether NS records should be checked to see if they are
102 addresses. Possible modes are "fail" (default for
103 named-compilezone), "warn" (default for named-checkzone) and
104 "ignore".
105 -o filename
107 Write zone output to filename. If filename is - then write to
108 standard out. This is mandatory for named-compilezone.
109 -r mode
111 Check for records that are treated as different by DNSSEC but are
112 semantically equal in plain DNS. Possible modes are "fail", "warn"
113 (default) and "ignore".
114 -s style
116 Specify the style of the dumped zone file. Possible styles are
117 "full" (default) and "relative". The full format is most suitable
118 for processing automatically by a separate script. On the other
119 hand, the relative format is more human-readable and is thus
120 suitable for editing by hand. For named-checkzone this does not
121 cause any effects unless it dumps the zone contents. It also does
122 not have any meaning if the output format is not text.
123 -S mode
125 Check if a SRV record refers to a CNAME. Possible modes are "fail",
126 "warn" (default) and "ignore".
127 -t directory
129 Chroot to directory so that include directives in the configuration
130 file are processed as if run by a similarly chrooted named.
131 -w directory
133 chdir to directory so that relative filenames in master file
134 $INCLUDE directives work. This is similar to the directory clause
135 in named.conf.
136 -D
138 Dump zone file in canonical format. This is always enabled for
139 named-compilezone.
140 -W mode
142 Specify whether to check for non-terminal wildcards. Non-terminal
143 wildcards are almost always the result of a failure to understand
144 the wildcard matching algorithm (RFC 1034). Possible modes are
145 "warn" (default) and "ignore".
146 zonename
148 The domain name of the zone being checked.
149 filename
151 The name of the zone file.
152
154 named-checkzone returns an exit status of 1 if errors were detected and
155 0 otherwise.
156
158 named(8), named-checkconf(8), RFC 1035, BIND 9 Administrator Reference
159 Manual.
160
162 Internet Systems Consortium
163
165 Copyright © 2004-2007, 2009 Internet Systems Consortium, Inc. ("ISC")
166 Copyright © 2000-2002 Internet Software Consortium.
167BIND9 June 13, 2000 NAMED-CHECKZONE(8)