1 .\" $NetBSD: zkt-conf.8,v 1.1.1.1 2015/07/08 15:37:49 christos Exp $
3 .TH zkt-conf 8 "February 22, 2010" "ZKT 1.0" ""
4 \" turn off hyphenation
8 zkt-conf \(em Secure DNS zone key config tool
52 command helps to create and show a config file for use by
53 the Zone Key Tool commands, which are currently
59 In general, the ZKT commands uses up to three consequitive sources for config
63 The build-in default parameters
66 The side wide config file or the file specified with option -c
67 overloads the built-in vars.
69 .I /var/named/dnssec.conf
70 or the one set by the environment variable ZKT_CONFFILE.
75 in the current zone directory also overloads the parameter read so far.
77 Because of the overload feature, none of the config files has to have
78 a complete parameter set.
79 Typically the local config file will have only those parameters which are
80 different from the global or built-in ones.
82 The default operation of
84 is to print the site wide config file (same as option
88 will print out the built-in defaults while
90 print those local parameters which are different to the global ones.
97 In all forms of the command, the parameters are changeable via option
99 .RB ( \-\-config-option ).
104 the confg parameters are written back to the config file.
105 This is useful in case of an ZKT upgrade or if one or more parameters are changed
111 checks some of the parameter for reasonable values.
114 Which config file is shown (or modified or checked) is determined by an option.
116 means the built-in defaults, option
118 is for the local config file and
120 specifies the site wide config file.
125 In the last form of the command, the
126 maximum TTL value of all the resource records of
128 is calculated and print on stdout.
129 Additional, the zonefile is checked if the key database
131 is included in the zone file.
134 is set, than the INCLUDE directive will be added to the zone file if
135 necessary, and the maximum ttl value is written to a local config file.
139 .BR \-h ", " \-\-help
140 Print out the online help.
142 .BR \-d ", " \-\-built-in-defaults
143 List all the built-in default parameter.
145 .BR \-s ", " \-\-sitecfg
146 List all site wide config parameter (this is the default).
148 .BR \-l ", " \-\-localcfg
149 List local config parameter which are different to the site wide config
154 all config parameters will be shown.
158 .BI \-V " view" ", \-\-view=" view
159 Try to read the default configuration out of a file named
160 .I dnssec-<view>.conf .
161 Instead of specifying the
165 option every time, it is also possible to create a hard or softlink to the
166 executable file and name it like
169 .BI \-c " file" ", \-\-config=" file
170 Read all parameter from the specified config file.
171 Otherwise the default config file is read or build in defaults
174 .BI \-O " optstr" ", \-\-config-option=" optstr
175 Set any config file parameter via the commandline.
176 Several config file options could be specified at the argument string
177 but have to be delimited by semicolon (or newline).
180 In case of showing the local config file parameter
182 this prints all parameter, not just the ones different to the site wide
183 or built-in defaults.
190 Print the built-in default config pars.
195 Write all the built-in defaults into the site wide config file.
198 .B "zkt-conf \-s \-O ""SerialFormat: Incremental; Zonedir: /var/named/zones"" \-w"
200 Change two parameters in the site wide
205 .B "zkt-conf \-w zone.db
208 .B "$INCLUDE dnskey.db"
209 to the zone file and set the maximum ttl paramter in the local config file
210 to the maximum ttl fond in any RR of
213 .SH ENVIRONMENT VARIABLES
216 Specifies the name of the default global configuration files.
220 .I /var/named/dnssec.conf
221 Default global configuration file.
222 The name of the default global config file is settable via
223 the environment variable ZKT_CONFFILE.
225 .I /var/named/dnssec-<view>.conf
226 View specific global configuration file.
229 Local configuration file (additionally used in
237 Copyright (c) 2005 \- 2010 by Holger Zuleger.
238 Licensed under the BSD Licences. There is NO warranty; not even for MERCHANTABILITY or
239 FITNESS FOR A PARTICULAR PURPOSE.
240 .\"--------------------------------------------------
242 dnssec-keygen(8), dnssec-signzone(8), rndc(8), named.conf(5), zkt-signer(8), zkt-ls(8), zkt-keyman(8),
245 "DNSSEC Operational Practices" by Miek Gieben and Olaf Kolkman,
247 DNSSEC HOWTO Tutorial by Olaf Kolkman, RIPE NCC
249 (http://www.nlnetlabs.nl/dnssec_howto/)