On 09/22/2009 06:37 AM, bert hubert wrote:
Gentelemen,
Could you perhaps try
http://svn.powerdns.com/snapshots/pdns-recursor-3.1.8-testing.tar.bz2
?
It has a default timeout of 1.5 seconds now, and this can be tuned
using the 'network-timeout' setting (in milliseconds).
Please let me know if it
On Fri, Sep 18, 2009 at 10:40 AM, bert hubert wrote:
> I'm currently looking in to this and I see why this has not been fixed
> - the timeout mechanism is rather crude, and may in fact not even be
> doing exactly what it is supposed to be doing. It is supposed to
> deliver a '1000ms' timeout right
On Fri, Sep 18, 2009 at 9:16 AM, Sten Spans wrote:
> As far as I know there currently is no way to improve powerdns-recursor's
> behaviour, short of modifying the source. I think Bert would appreciate a
> well tested patch which improves the behaviour, although only if it doesn't
> hurt lookup per
On Wed, 16 Sep 2009, Andre Recnik wrote:
Recently my ISP has been doing some 'upgrades' which as caused very high
latency in the last few days. This latency is between 2.1 and 5.6 seconds
(as seen in a trace route to outside my network).
As a result almost all look-ups are failing - and I ha
I have been using PowerDNS and the PowerDNS recursor to host two name
servers, for the last three months, in a 30+ user environment with no
problems.
Recently my ISP has been doing some 'upgrades' which as caused very high
latency in the last few days. This latency is between 2.1 and 5.6
sec
