Groups > comp.protocols.dns.bind > #15898

Re: $INCLUDE Kexamle.com.+007...

From	"@lbutlr" <kremels@kreme.com>
Newsgroups	comp.protocols.dns.bind
Subject	Re: $INCLUDE Kexamle.com.+007...
Date	2020-07-05 16:02 -0600
Message-ID	<mailman.606.1593986520.942.bind-users@lists.isc.org> (permalink)
References	<84EA4A1E-A47D-4CB2-8FEB-B780B9A09C94@kreme.com> <alpine.DEB.2.20.2007051657510.15871@grey.csi.cam.ac.uk> <5CEE1B71-98F2-4C39-B552-B3427EFDBDBC@kreme.com>

Show all headers | View raw

On 05 Jul 2020, at 10:12, Tony Finch <dot@dotat.at> wrote:
> @lbutlr <kremels@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 ...

Heh.

> So it sounds like "the current directory" is the answer to your question.

That would certainly explain why it fails then.

> 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.

Ah, that would be good. When I resolve the other issue I posted about I will check that.

My configuration started in … um… 1995? I'm sure I should start all over with the 9.16 manual from scratch, but you know, I have all this TV to watch. 😃

> Does that make sense?

It does, and thank you.

-- 
It's against my programming to impersonate a deity.

Back to comp.protocols.dns.bind | Previous | Next | Find similar

Thread

Re: $INCLUDE Kexamle.com.+007... "@lbutlr" <kremels@kreme.com> - 2020-07-05 16:02 -0600

csiph-web