[Pdns-users] Additional NSEC3-Record in Response - DNSSEC Validation fails

2011-08-22 Thread Michael Braunoeder
Hi, I did some more DNSSEC-testing and found another bug: My setup looks like this: Bind accting as Master server, serving a presigned zone. PDNS 3.0 accting as Slave server, PRESIGNED=1 and NSEC3PARAM is set in Domainmetatable. When querying for an undefined records, PDNS adds an

[Pdns-users] pdns generates records when presigned=1 is set

2011-08-09 Thread Michael Braunoeder
Hi, I noticed a strange dnssec behavoir with pdns 3.0 (and postgresql-backend): I have loaded a zone into the db, the zone is unsigned but the domainmetadata presigned is set to 1. Everything works fine, except if I ask for a non-available record (with dnssec-ok flag set in the query), then

[Pdns-users] PowerDNSSEC

2010-06-25 Thread Michael Braunoeder
Hi, I'm currently evaluating the PowerDNSSEC implementation and found 2 issues: -) Is it possible to disable the signing-on-demand feature? I want the powerdns to act as slave to a hidden-master which does the signing of the domain, and the powerdns should just serve the signed zone (without