> On Jan 9, 2016, at 3:28 PM, Pieter Lexis wrote:
>
> Hi Nick,
>
> On Sat, 9 Jan 2016 14:48:12 -0600
> Nicholas Williams wrote:
>
>> But the documentation says the opposite. It says NOT to create
>> NSEC(3) records (in fact, zone2sql intentionally ignores them, even
>> for presigned zones), b
Hi Nick,
On Sat, 9 Jan 2016 14:48:12 -0600
Nicholas Williams wrote:
> But the documentation says the opposite. It says NOT to create
> NSEC(3) records (in fact, zone2sql intentionally ignores them, even
> for presigned zones), because (again, it says) PowerDNS generates
> then automatically, eve
Sent from my iPhone, so please forgive brief replies and frequent typos
> On Jan 9, 2016, at 14:22, Pieter Lexis wrote:
>
> Hi William,
>
> On Sat, 9 Jan 2016 13:41:51 -0600
> Nick Williams wrote:
>
>> I can’t think of anything I missed. And, clearly, PowerDNS is
>> correctly generating NSE
Hi William,
On Sat, 9 Jan 2016 13:41:51 -0600
Nick Williams wrote:
> I can’t think of anything I missed. And, clearly, PowerDNS is
> correctly generating NSEC3 records. But it’s not signing those
> records.
This is because the zone is presigned, PowerDNS cannot generate the
signatures on the NS
So, I think I’ve almost got this, but I’m having a problem with the pre-signed
zone’s NSEC3 RRSIGs. Here’s what I did:
I already have a live-signed zone (my-zone.com) that works perfectly. A-records
come with automatic RRSIGs, SOA record comes with an RRSIG, NS records come
with an RRSIG, etc.
It works if you use HTTP/1.1 compatible responses. RFC says that you either
need to send your response chunked or set content-length. YaHTTP will check
and enforce this.
Aki
On Sat, Jan 09, 2016 at 11:10:19AM +0200, Aleksey Chudov wrote:
> Finally I found the cause of the problem. PowerDNS Remote
> 10 instances ??
> Im experimenting with 4 recursor instances because I have plenty of cpu and
> ram:
>
> top - 16:20:08 up 8 days, 7:36, 3 users, load average: 0.06, 0.05, 0.05
> Tasks: 383 total, 1 running, 382 sleeping, 0 stopped, 0 zombie
> Cpu(s): 5.5%us, 2.5%sy, 0.0%ni, 91.4%id,
Well, after several hours of sending dnsdist stats i see embarrassing
numbers, considering the load and memory usage and still i got a lot 200 ms
response time (dnsdist.dns1j4s0n.main), what could be the cause of this,
network latency or am i totally messed up the recursor config? Each
instance has
Finally I found the cause of the problem. PowerDNS Remote HTTP Backend
works only with 'Content-Length' header.
So, the following code works until 'Content-Length' header exists.
import BaseHTTPServer
class HTTPRequestHandler(BaseHTTPServer.BaseHTTPRequestHandler):
def do_GET(self):
