Local Recursive DNS Resolvers
Cluster focuses on recommendations to run personal recursive DNS resolvers like Unbound or systemd-resolved instead of relying on ISP or default resolvers, discussing setup ease, privacy benefits via DoT/DoH, and compatibility issues.
Activity Over Time
Top Contributors
Keywords
Sample Comments
The DNS resolver is configurable, not hard coded. Forcing a switch would require OS vendors to ignore the resolver issued via DHCP, which would not work on many corporate networks that block outbound DNS not via their resolver.
Why not run your own recursive resolver? It's very easy to set up - worried about leaking your IP address to authoritative DNS servers?
Why not a user-space DNS resolver, such as Hickory DNS?
DoT and running your own recursive resolver is better still.
Does running your own recursive resolver (that queries the root servers directly) get around this?
Doesn't systemd-resolved support it?
They already have regular dns resolvers. This helps in DoH adoption and decentralization.
When are operating systems going to start resolving names themselves instead of relying on ISP caches?
I stumbled upon this when researching wether it was something to set up with my pi as DSN resolver but it was kinda a pita, does implementing DoT would be faster?
You can just run unbound or similar and do your own recursive resolving.