I'm using Pi-hole with unbouwd as recursive resolver, all working fine.
However I would like to have advice concerning disabling DNSMASQ & cache in Pihole.
Some guides say it so others don't...
NOT a developer...
I'm running pihole-FTL + unbound (compiled) + redis with dnsmasq cache-size=0 for almost a month, NO performance degradation.
The dsnmasq cache is still used (even with size 0) for all reverse lookup queries.
The discussion, to modify pihole's dnsmasq cache-size began when somebody was investigating the settingproxy-dnssec. Setting the cache-size to 0 solved some, but not all problems with dnssec being handled by unbound.
If I understood correctly, DNSSEC setting in Pi-Hole only adds the DNSSEC info in the log?
Why is it recommended to disable?
(very willing to disable if there are benefits to it, if not, I'd rather keep the extra info in 1 view within the Pi-Hole interface...)
This was recommended when we were running an older version of dnsmasq that had some DNSSEC bugs. The version currently shipping with Pi-hole is 2.8.2 and does not have this problem. I think the bug was fixed in either 2.8.0 or 2.8.1.