Is it possible to set pi-hole's cache to tmp in tmpfs?

[jfb]

@anon62498003

I’ve set in: /etc/dnsmasq.d/01-pi-hole.conf

cache-size=100000

This is of no benefit. Even with the default cache size of 10,000, you will likely never have a full cache. The cache information is retrieved with the following command and the example output is from a Pi-Hole that serves 21 clients (many of them IOT with repeated DNS queries).

echo ">cacheinfo" | nc 127.0.0.1 4711
cache-size: 10000
cache-live-freed: 0
cache-inserted: 9578

See the thread referenced below for details.

What is the optimal cache size?

Thanks for this article, it explains things very clearly. I am using the beta and unbound as described and it works very well for me. I am happy to accept a small performance penalty for the privacy benefits. In actual fact we have no perceivable performance hit - not noticed at all. I did experiment with setting a larger cache (up from the default 10,000 to 250,000) but found I could only make this work by editing 01-pihole.conf. When I edited /etc/dnsmasq.conf Pi-hole's DNS services would…

The cache is in memory and is not written to disk. There is no file to redirect to tmp or tmpfs.