[Pdns-users] ipv6 reverse lookup timeout error
Peter van Dijk
peter.van.dijk at netherlabs.nl
Mon Dec 2 13:38:45 UTC 2013
On Dec 1, 2013, at 22:18 , tsboj17 wrote:
> Nov 30 20:17:15 dbtest2 pdns_recursor: 0  question for
> from 127.0.0.1
> Nov 30 20:17:15 dbtest2 pdns: Query: select
> content,ttl,prio,type,domain_id,name from records where type='SOA' and
.. SQL queries
> *Nov 30 20:17:16 dbtest2 pdns_recursor: 0  answer to question
> 0 answers, 0 additional, took 1 packets, 0 throttled, 1 timeouts, 0 tcp
.. more SQL queries
> I changed the address in random places so it's not correct of course (it's
> just an example so it does not have to be correct).
> The problem is:
> The pdns begins decrypt the address from query to query. Suddenly the
> service reach the default network-timeout limit(because every query has
> execution time of course) and then it sends a error message (rcode=2). It
> can be seen in the log, I emphasize with Bold style. After that message the
> pdns continue the decrypt but naturally it does not get to me.
> Of course if I raise the network-timeout value higher, it works great
> because the service has time to finish the queries. In that case, I got
> correct result, so that part is good.
> It is a pdns bug or I missed something in the config file? I don't know how
> can i fix this.
> I could not find same probem in google, that's why I'm writing to here.
It is not a pdns bug. It is also not a misconfig. If your postgresql backend can't answer these questions, in series, in under one second, you need to optimize it on that end.
What might help on the pdns-server config side is to increase some of the cache TTLs (negquery-cache-ttl mostly comes to mind).
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Pdns-users