dot at dotat.at
Sun Jul 5 16:12:04 UTC 2020
@lbutlr <kremels at kreme.com> wrote:
> When a domain configuration file contains an include line for the key,
> where is that include looking for the key file?
... good question, I have avoided having to find that out ...
> I'm in a situation where the keys seems to work fine for updating
> DNSSEC, but nsdiff complains the key file is not found.
Well, nsdiff uses named-compilezone to canonicalize zone files, and the
named-compilezone manual lists a couple of options that affect $INCLUDE:
Chroot to directory so that include directives in the configura‐
tion file are processed as if run by a similarly chrooted named.
chdir to directory so that relative filenames in master file
$INCLUDE directives work. This is similar to the directory
clause in named.conf.
So it sounds like "the current directory" is the answer to your question.
However, I don't think you need to $INCLUDE key files. I think maybe that
used to be a thing when signing a zone had to involve dnssec-signzone? But
nowadays even dnssec-signzone will automatically insert public keys into
the signed zone.
When you're doing automatic signing with named (which you have to do if
you are using nsupdate to alter the zone), the keys are included in the
signed zone based on their timing metatata, which you can set with
dnssec-settime. [There's also the new key policy stuff which I have not
yet tried out properly.]
So the actual answer is, you don't explicitly $INCLUDE the keys in the
zone, so questions about current directories do not arise.
Does that make sense?
f.anthony.n.finch <dot at dotat.at> http://dotat.at/
Lough Foyle to Carlingford Lough: Southwest veering west, 6 to gale 8, then
veering northwest 4 to 6 later. Moderate or rough, becoming slight or moderate
south of rathlin island. Showers,thundery at first. Good, occasionally
More information about the bind-users