#selfhosting #selfhosted #dns #quad9
@train Ahm, why would I? It's running on my hosts in my homelab...?
Ooooh, am I completely misinterpreting your question? You were talking about recursive DNS servers (upstream servers like 8.8.8.8), not about recursing servers you run yourself? 🤦
@train Ah, in that case I'm really sorry about the noise.
I must admit that I haven't done much thinking in this regard. I've got the OpenDNS servers configured, but that's not based on much research or anything. I just figured: Cisco doesn't make it's money with DNS servers, so it should be reasonably safe from any shenanigans.
@train
adguard-home primary, blocky secondary, with nominally identical blocklists and configs. (It is theoretically possible to scale adguard now, but I'm used to this setup.)
Both point to secure, trusted upstreams that are not google because my provider does evil manipulation of DNS traffic (and smtp, probably others) when they can and I kinda wish that was illegal.
https://adguard.com/en/adguard-home/overview.html https://0xerr0r.github.io/blocky
@train +1 for unbound on OPNsense.
Also tried NextDNS which was really really nice. But unbound works so good and fast with the caching, it’s fine for me. Maybe not so fast like NextDNS or Cloudflare but not really noticeable slower in everyday use.
@train #unbound running here as a #recursive #DNS #resolver.
Not too bad after a while.