I found a packet requesting dnskey record at priming,in spite of removing
"validator" from my config.
What is the purpose of this function?
I think this function may cause trouble with KSK rollover.
--
--
T.Suzuki
Petr Špaček via Unbound-users wrote:
> Well, the spec is from 1987. Even the meaning of MUST/SHOULD etc. was
> not standardized yet back then ...
Even worse, this language appears to have been copied verbatim from RFC
883, which is even older (1983) :-)
--
Robert Edmonds
edmo...@debian.org
On 28.7.2017 00:15, Jacob Hoffman-Andrews via Unbound-users wrote:
> On 07/27/2017 01:28 PM, Robert Edmonds wrote:
>> Jacob Hoffman-Andrews via Unbound-users wrote:
>>> I'm trying to write some documentation for users of Let's Encrypt about
>>> CAA. I believe it's the case that
Le mercredi 2 août 2017, 08:46:31 CEST W.C.A. Wijngaards via Unbound-users a
écrit :
> Hi,
>
> Also,
> local-zone: "2.2.0.0.6.1.0.2.0.0.d.f.ip6.arpa." nodefault
> has to be d.f.ip6.arpa nodefault, to disable the default zone that is
> upwards from your private zone.
>
> Best regards, Wouter
>
Hi Dave,
What must be happening is that your authority server for the combine
192.168 stub clause, does not actually host a 192.168 reverse zone. And
that causes unbound to detect that the delegation is lame. Lameness
check only performed for authoritative servers (i.e. stub zones). And
now
Hi,
Also,
local-zone: "2.2.0.0.6.1.0.2.0.0.d.f.ip6.arpa." nodefault
has to be d.f.ip6.arpa nodefault, to disable the default zone that is
upwards from your private zone.
Best regards, Wouter
On 01/08/17 18:29, Eric Luehrsen via Unbound-users wrote:
> dnsmasq is a forwarding resolver and you
