On Wed, 13 Apr 2011 12:11:34 -0700 bert hubert
bert.hub...@netherlabs.nl wrote:
Try reproducing with 'threads=1'. You may be seeing hits from
multiple separate caches.
You are telling me that each thread maintains its own cache.
I restarted with threads=1 but I still see the same.
Having
On Thu, Apr 14, 2011 at 09:40:58AM -0700, Alfred B. M. Cordero wrote:
On Wed, 13 Apr 2011 12:11:34 -0700 bert hubert
bert.hub...@netherlabs.nl wrote:
Try reproducing with 'threads=1'. You may be seeing hits from
multiple separate caches.
You are telling me that each thread maintains its
On Thu, 14 Apr 2011 10:13:05 -0700 bert hubert
bert.hub...@netherlabs.nl wrote:
Ok - in that case it may be good to know that the output of the
Lua scripts is only cached in the packet cache, and not within the
main dns cache.
So whatever TTL you set, the result will not be cached for longer
Using the postresolve hook in lua to alter TTL that are too low.
I log queries that hit the lua code and I see log events for
that same host that occur within the same one second period
and sometimes within a few or more seconds. I don't understand
why there are multiples. Shouldn't they be cached
On Wed, Apr 13, 2011 at 11:53:35AM -0700, Alfred B. M. Cordero wrote:
Using the postresolve hook in lua to alter TTL that are too low.
I log queries that hit the lua code and I see log events for
that same host that occur within the same one second period
and sometimes within a few or more
