On Jul 15, 2009, at 12:59 PM, Dave Sparro wrote:
Scott Haneda wrote:
On Jul 15, 2009, at 12:29 PM, Dave Sparro wrote:
Scott Haneda wrote:
... However, I would like to just get DNS response times.
Perhaps take the list of hosts and feed them to a iterative
script calling dig, and fish out th
Scott Haneda wrote:
On Jul 15, 2009, at 12:29 PM, Dave Sparro wrote:
Scott Haneda wrote:
... However, I would like to just get DNS response times.
Perhaps take the list of hosts and feed them to a iterative script
calling dig, and fish out the response time? This does add the
problem of re
On Jul 15, 2009, at 12:29 PM, Dave Sparro wrote:
Scott Haneda wrote:
... However, I would like to just get DNS response times.
Perhaps take the list of hosts and feed them to a iterative script
calling dig, and fish out the response time? This does add the
problem of redirects of course w
Scott Haneda wrote:
... However, I would like to just get DNS response times.
Perhaps take the list of hosts and feed them to a iterative script
calling dig, and fish out the response time? This does add the
problem of redirects of course would not be followed, so I would have
to pre-fetch a
Hello.
powerdns-recursor - the best. :)) Over 20k req/sec - feel good.
As variant try to use small TTL like:
bind:
max-ncache-ttl 1;
max-cache-ttl 1;
powerdns-recursor
cache-ttl=1
default-ttl=1
Scott Haneda wrote:
Hello, this may not entirely be related to BIND/named, though I believe
it is.
Hello, this may not entirely be related to BIND/named, though I
believe it is.
I am working on a set of benchmarks to test the resolving speed of
different recursive DNS providers. My plan is call an http resource,
and see how long it takes to resolve that host, as well as all
embedded h
6 matches
Mail list logo
