"query time" (caching) +plus
how I audit if a query is resolved from my local DNS or by external DNS?
cheers!
Pol
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
not sure hwat you mean but likely
https://kb.isc.org/article/AA-01315/0/prefetch-performance-in-BIND-9.10.html
exactly what I looking for!
cheers!
Pol
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
Am 20.09.2016 um 00:12 schrieb Pol Hallen:
In the third case, the A records had expired from the cache (since the
TTL on those records is 300 seconds = 5 minutes), so your resolver
needed to fetch a fresh set from the yahoo.it nameservers -- the NS
records of which were most likely cached from
how I audit if a query is resolved from my local DNS or by external DNS?
cheers!
Pol
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
In the third case, the A records had expired from the cache (since the TTL on
those records is 300 seconds = 5 minutes), so your resolver needed to fetch a
fresh set from the yahoo.it nameservers -- the NS records of which were most
likely cached from the first lookup -- but it didn't need to
-boun...@lists.isc.org] On Behalf Of Pol
Hallen
Sent: Monday, September 19, 2016 5:43 PM
To: bind-users@lists.isc.org
Subject: about "query time" (caching)
Hi all,
I'm struggling about "query time" :-/
Using bind 9.9.5, I configurated it as caching proxy:
dig yahoo.it @192.16
Hi all,
I'm struggling about "query time" :-/
Using bind 9.9.5, I configurated it as caching proxy:
dig yahoo.it @192.168.1.212
[...]
96msec
second time:
dig yahoo.it @192.168.1.212
[...]
1msec
seems it works but: if I waiting (ie 5 minutes) and I re-run same
command, "query time" was
7 matches
Mail list logo
