I use unbound on a local machine to server my entire LAN, but there is one giant thing to understand about it. It will massively speed up cached queries in a wa

I use unbound on a local machine to server my entire LAN, but there is one giant thing to understand about it. It will massively speed up cached queries in a way you won't get with any internet accessible resolver. BUT, it will slow down everything else simply because its another layer in the lookup cake. Which doesn't sound bad since everything will end up cached, until you notice all the cool people have decided that DNS forms part of their load/failover scheme and have set the TTL to just a few seconds, which effectively either keeps unbound constantly fetching those addresses to keep them fresh, or you pay the unbound overhead penalty all the time on your local machines. And yes, unbound can be configured to ignore TTL's below a certain value, but that has its own problems. So, yes, run your own resolver, just be aware that it has tradeoffs. One of the big pluses is that you can configure it do to DOH/etc and then serve everything on your network unencrypted DNS that has been previously validated/etc.