I run the same setup, local resolver that recurses from the roots, and I don't cache anything other than what my systems actually request. If I hit a new site, I pay the penalty for not having certain information cached.
Hows the DNS server to know what to pre-cache to reduce lookup times?
Even for something that is not in the cache DNS is lightweight and quick, and I have full control over when to flush it, and have logs.
I am not huge fan of the trend of various device manufacturers (looking at you Google, and now Apple too) sending queries over DoH instead of using the local resolver on my network :/
I run the same setup, local resolver that recurses from the roots, and I don't cache anything other than what my systems actually request. If I hit a new site, I pay the penalty for not having certain information cached.
Hows the DNS server to know what to pre-cache to reduce lookup times?
Even for something that is not in the cache DNS is lightweight and quick, and I have full control over when to flush it, and have logs.
I am not huge fan of the trend of various device manufacturers (looking at you Google, and now Apple too) sending queries over DoH instead of using the local resolver on my network :/