Hi,
Fixed the documentation in the man page to more clearly state that
chroot is enabled by default. In addition, it lists the default setting
for it as well. If you are using man pages online, that gets updated
when we release a new version, the man page source is already available
in the
Hi,
On 26/07/18 19:53, ѽ҉ᶬḳ℠ via Unbound-users wrote:
You can start the auto-trust-anchor-file rotation by providing a file
like for trust-anchor-file: a plain text file with DNSKEY or DS records
in there.
>> I tried this with (in conf)
>>
>> auto-trust-anchor-file:
>>> You can start the auto-trust-anchor-file rotation by providing a file
>>> like for trust-anchor-file: a plain text file with DNSKEY or DS records
>>> in there.
>>>
>>>
> I tried this with (in conf)
>
> auto-trust-anchor-file: "/etc/unbound/trusted-key.key"
> auto-trust-anchor-file:
>> You can start the auto-trust-anchor-file rotation by providing a file
>> like for trust-anchor-file: a plain text file with DNSKEY or DS records
>> in there.
>>
>>
I tried this with (in conf)
auto-trust-anchor-file: "/etc/unbound/trusted-key.key"
auto-trust-anchor-file:
>> to my understanding it is feasible to have DNSSEC served for private
>> zones in stub-zone, requiring a trusted key entry with the public key
>> in config - that would be trough > trusted-keys-file: <, right?
> trusted-keys-file reads the BIND syntax for a key statement, but not the
> managed
Hi,
On 26/07/18 16:15, ѽ҉ᶬḳ℠ via Unbound-users wrote:
> Hi,
>
> to my understanding it is feasible to have DNSSEC served for private
> zones in stub-zone, requiring a trusted key entry with the public key
> in config - that would be trough > trusted-keys-file: <, right?
trusted-keys-file
