[Pdns-users] High latency on recursion without cache
bert hubert
bert.hubert at powerdns.com
Mon Jan 19 19:57:00 UTC 2015
On Fri, Jan 16, 2015 at 01:34:45PM -0300, Ciro Iriarte wrote:
> This were the queries sent from a client:
>
> 2015-01-16 13:04:38 dig @server 3.redhat.pool.ntp.org <-- NXDOMAIN, my
> mistake
> 2015-01-16 13:15:35 dig @server 2.redhat.pool.ntp.org <-- NXDOMAIN, my
> mistake
> 2015-01-16 13:15:52 dig @server 2.centos.pool.ntp.org <-- NOERROR
Hi Ciro,
Sadly your trace is interleaved with a bunch of other queries which make it
harder to see what is going on.
The trace for '2.centos.pool.nto.org' stops in the middle:
Jan 16 13:15:53 rdns4m01 pdns_recursor[7294]: [2] dns2.udel.edu.: accept answer 'adns3.upenn.edu.|AAAA|2607:f470:1003::3:c' from 'edu.' nameservers? YES!
Jan 16 13:15:53 rdns4m01 pdns_recursor[7294]: [2] dns2.udel.edu.: determining status after receiving this packet
Jan 16 13:15:53 rdns4m01 pdns_recursor[7294]: [2] dns2.udel.edu.: got NS record 'udel.edu.' -> 'dns1.udel.edu.'
How did you gather or select the trace output? Is it possible you missed some output?
Also, what Lua scripts do you run? Might these be interfering in some way?
Bert
More information about the Pdns-users
mailing list