Prefetch Popular Domains to Improve Cached Response Frequency

[yubiuser]

@Matt

Implementation of prefetching, especially TTL EOL Prefetching designed to mimic Unbound prefetching, could resolve the main issue driving users to modify cache size on Pi-hole to 0, against developer recommendation , as Unbound would now be receiving those near-EOL requests typically absorbed by Pi-Hole. Everyone wins.

@Matt

But the specific phrasing of his statement was a bit hard to follow - when he says "prefetching might not have an effect", what he's saying is "if the algorithm follows what is stated in the mail thread, prefetching may not happen at all if Pi-hole caches queries".

I guess you have read the whole topic you linkes above? I also thought that unbound might not prefetch if I leave pihole's cache enabled (as I understood the explanation in the mail thread) so I just went and looked at the unbound stats: a lot of prefetching happened despite pihole's cache enabled. My resume was that the description in the mail is not accurate (any more?) .

Add CACHE_SIZE to setupVars.conf

Thank you for your effort. In my opinion your observation what's in the source code does not match the explanation given in the link (I believe the explanation is wrong/outdated, not the code ). The source code suggests that all DNS queries are prefetched. This in line with what I see because a lot gets prefetched. total.num.queries=5292 total.num.cachehits=4460 total.num.cachemiss=832 total.num.prefetch=2735 --> Disabling Pihole's cache is not necessary, prefetching happens …