[Pdns-users] Lower limit to network-timeout recursor config parameter ?
bert.hubert at powerdns.com
Mon Sep 12 12:18:00 UTC 2016
The story is, PowerDNS Recursor makes a sweep every so many packets to find
out if there are timeout conditions.
So on a loaded recursor, you might get very accurate timeouts even below
Can you redo your tests with traffic load?
On Thu, Sep 08, 2016 at 03:03:58PM +0200, Florent Krieg wrote:
> Hmmm sorry to spam, doesn't seem relevant, we're using a more recent
> Investigation still going on...
> 2016-09-08 15:00 GMT+02:00 Florent Krieg <flokrrr at gmail.com>:
> > Ok, that may be
> > *Make timeouts for queries to remote authoritative servers configurable
> > with millisecond granularity. In addition, the old code turned out to
> > consider the timeout expired when the integral number of seconds since 1970
> > increased by 1 - which on average is after 500ms. This might have caused
> > spurious timeouts! New default timeout is 1500ms. See network-timeout
> > setting for more details. Code in commit 1402.*
> > :)
> > Florent
> > 2016-09-07 18:18 GMT+02:00 Florent Krieg <flokrrr at gmail.com>:
> >> Hello everybody,
> >> Just wanted to know if there was any lower limit to the network-timeout
> >> config param on the recursor?
> >> I have a situation where I want to setup in advance a zone forward to
> >> nameservers not already created in my network, and to avoid long queries I
> >> wanted to setup for instance network-timeout to like 20ms on our recursors.
> >> I have found however that setting this param to less than 500ms is
> >> useless, as it seems to reach its lower value at 500ms. Is that expected ?
> >> Thanks in advance.
> >> Best regards
> >> Florent
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
More information about the Pdns-users