RE: about "query time" (caching) +plus
You could turn on debugging, to be sure. Or, you could just dump your cache and see what's in it or not, expired or not. Anything lacking a valid, unexpired cache entry is going to require communication with the outside to resolve, which is going to introduce some measure of delay. - Kevin -Original Message- From: Pol Hallen [mailto:bin...@fuckaround.org] Sent: Monday, September 19, 2016 6:14 PM To: Darcy Kevin (FCA); bind-users@lists.isc.org Subject: Re: about "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 bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: about "query time" (caching)
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 bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: about "query time" (caching)
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 the first lookup -- but it didn't need to follow the referral chain all of the way down from the root. 19 msec. thanks Kevin, now it's clear is there a way to keep update cache of queries users will do? not sure hwat you mean but likely https://kb.isc.org/article/AA-01315/0/prefetch-performance-in-BIND-9.10.html ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: about "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 bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: about "query time" (caching)
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 follow the referral chain all of the way down from the root. 19 msec. thanks Kevin, now it's clear is there a way to keep update cache of queries users will do? 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 https://lists.isc.org/mailman/listinfo/bind-users
RE: about "query time" (caching)
In the first case, your resolver probably had to resolve all levels of the hierarchy from the root all of the way down to the leaf node (root, .it, yahoo.it and then the leaf records). 96 msec. In the second case, the answer was cached and so your resolver didn't have to talk to anything on the Internet at all. 1 msec. 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 follow the referral chain all of the way down from the root. 19 msec. This all seems reasonable and expected, to me. - Kevin -Original Message- From: bind-users [mailto:bind-users-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.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 increased: 19msec why? If the record "yahoo.it" is inside cache why after 5 minutes "query time" is 19msec? thanks all for help! 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 https://lists.isc.org/mailman/listinfo/bind-users ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
