<div dir="ltr"><div><div><div>Hi all,<br><br></div>Currently, I use the latest release of unbound 1.5.2 compilled by myself on the Debian wheezy. I have some confusion of the using the the "prefetch" option in the unbound.conf file. Let me described it as follows:<br><br></div>1- From the manual of unbound.conf, i.e., `man unbound.conf', I can get the following <br></div> notes on this option:<br><br><div><div><div><div> prefetch: <yes or no><br> If yes, message cache elements are prefetched before they expire<br> to keep the cache up to date. Default is no. Turning it on<br> gives about 10 percent more traffic and load on the machine, but<br> popular items do not expire from the cache.<br clear="all"><div><div><br></div><div>2- From the following webpage: <a href="https://calomel.org/unbound_dns.html">https://calomel.org/unbound_dns.html</a>,<br></div><div> I can get the explanation on this option as follows:<br><br> <br></div><div><pre class=""> # perform prefetching of close to expired message cache entries. If a client
# requests the dns lookup and the TTL of the cached hostname is going to
# expire in less than 10% of its TTL, unbound will (1st) return the ip of the
# host to the client and (2nd) pre-fetch the dns request from the remote dns
# server. This method has been shown to increase the amount of cached hits by
# local clients by 10% on average.
prefetch: yes<br></pre><pre class="">As you can see, the above two explanations on the mechanism of prefetching in unbound are not so<br></pre><pre class="">well the same. Could someone please give me some hints on the this thing?<br><br></pre><pre class="">Regards<br></pre><pre class=""></pre></div><div>--<br><div class="gmail_signature">Hongyi Zhao <<a href="mailto:hongyi.zhao@gmail.com">hongyi.zhao@gmail.com</a>> <br>Xinjiang Technical Institute of Physics and Chemistry<br>Chinese Academy of Sciences <br>GnuPG DSA: 0xD108493</div>
</div></div></div></div></div></div></div>