Please correct me if I am mistaken, but unless there’s a local resolver for every single one of your clients, aren’t the DNS requests sent in plaintext to the upstream of your local resolver?
replyThat might not be an issue for your situation, but I recall the benefit of something like Quad9’s offering is the encryption between client and their endpoint(s), particularly for untrusted ISP or similar.
Yes, that's a real benefit in many situations. Everything on your lan can do normal DNS queries to your local forwarder, which talks DNS over TLS or DNS over HTTPS to Quad9.
replyDownside is Quad9 can see all your DNS traffic. But without it if you run your own recursive resolver your ISP sees all your queries, and many others see portions of them, unencrypted.
> But without it if you run your own recursive resolver your ISP sees all your queries, and many others see portions of them, unencrypted.
replyThis hopefully shouldn't be an issue for long with stuff like RFC 9539 and OOTS/SVCB.
> I prefer to run my own local recursive resolver.
replyUsed to be fine. I stopped doing it when average TTL dropped to 300 seconds and it takes far too long for my local recursor to get the answer >100ms, when 3rd party resolver delivers in <10ms.
You don't have to obey TTL. You can use Unbound options like:
reply cache-min-ttl: 3600 // seconds
cache-min-negative-ttl: 3600 // seconds
serve-expired: yes
serve-expired-client-timeout: 20 // milliseconds to wait for resolution before serving the old value to the client