l...@consolejunkie.net wrote:
On 2015-04-24 21:35, Michael Ströder wrote:
Michael Ströder wrote:
We're currently testing DNSSEC validation with libunbound 1.5.3 with all
the RRs
retrieved through a pdns-recursor (also tested 3.7.2).
It seems that
1. libunbound does not explicitly retrieve the
On Fri, Apr 24, 2015 at 11:07:46PM +0200, l...@consolejunkie.net wrote:
> The answer I got was:
>
> The validation is in comparison the easy part, changing the recursor
> to return the DNSSEC-information is more work.
We're on it people!
http://blog.powerdns.com/2015/02/23/powerdns-development-pl
On 2015-04-24 21:35, Michael Ströder wrote:
Michael Ströder wrote:
We're currently testing DNSSEC validation with libunbound 1.5.3 with
all the RRs
retrieved through a pdns-recursor (also tested 3.7.2).
It seems that
1. libunbound does not explicitly retrieve the RRSIG RRs and
2. pdns-recurs
Michael Ströder wrote:
We're currently testing DNSSEC validation with libunbound 1.5.3 with all the RRs
retrieved through a pdns-recursor (also tested 3.7.2).
It seems that
1. libunbound does not explicitly retrieve the RRSIG RRs and
2. pdns-recursor does not return them when not explicitly re
HI!
We're currently testing DNSSEC validation with libunbound 1.5.3 with all
the RRs
retrieved through a pdns-recursor (also tested 3.7.2).
It seems that
1. libunbound does not explicitly retrieve the RRSIG RRs and
2. pdns-recursor does not return them when not explicitly request (qtype
ANY
