News for hackers. Stuff that matters.
Re:Choosing a Public DNS Resolver by exiguus on Saturday June 27, 2026 @11:14PM (#48703986)
Most important and super privacy/security related topic: DNS. Instead of choosing a public one. Host your own infrastructure. You don't need public instances. Just run ADGUARD or unbound/dnsmasq/dnsdist in recursive mode on your router or machine. And you can set limits and block-lists to your needs.
Re:Choosing a Public DNS Resolver by abcdefg12 on Sunday June 28, 2026 @05:12AM (#48705680)
And your isp can record all your queries
Re:Choosing a Public DNS Resolver by exiguus on Sunday June 28, 2026 @07:33AM (#48706450)
Do you mean when communicating directly with a root DNS server over unencrypted UDP or TCP? You're right. There's currently no universal way to encrypt direct queries to root DNS servers. To work around this, the best approach is to host your own public DNS server outside your untrusted ISPs network and connect to it securely using DoH, DoQ, or DoT. Alternatively, you can rely on a trusted third-party public DNS provider that supports encrypted connections. In the end, there's no perfect solution. You have to choose who to trust. Personally, I trust my ISP more than external DNS providers. For anonymity you could route your DNS root queries throe tor or a VPN for the cost of performance.

I also used third-party public resolvers before. Mainly FFM (its not on the list) but non-profit, EU and encrypted. If you boil down the list (from the website) to this categories, you have 4 providers. You can trust, in my opinion. But the problem with all this provider is, that you ran quick into rate limits or some query type restrictions. Especially if you run your own mail server or other DNS expensive task.

Re:Choosing a Public DNS Resolver by microgpt on Sunday June 28, 2026 @08:39AM (#48706783)
Your friends and family probably don't know what DNS privacy is. If they do know, they'll already be hosting their own. They will care if it works better. When my ISP fucked up DNS once I had my family use mine instead.
Re:Choosing a Public DNS Resolver by abcdefg12 on Sunday June 28, 2026 @03:36PM (#48710760)
That’s fine if you don’t care about privacy as long as you’re conscious about that. Dnscrypt is simple enough to use otherwise
Re:Choosing a Public DNS Resolver by exiguus on Monday June 29, 2026 @06:19AM (#48717282)
How do you use DNSCrypt on Android or iOS?

On my notebooks, I run two Docker instances of AdGuards dnsproxy, using my own DNSCrypt resolvers as upstream servers. This setup provides anonymity from the resolver and protects against man-in-the-middle attacks, since DNSCrypt authenticates DNS responses. However, root DNS queries from the upstream remain unencrypted. Additionally, not all nameservers support DNSSEC, so a fallback is often needed. Which can still leave the upstream vulnerable to man-in-the-middle attacks. Of course, DNSCrypt is more secure (authentication, no bootstrapping), faster and anonym (against the resolver). But i think it is still not useable for "normal" people. And as a provider, the setup is more complex then DoH, DoT or DoQ, because of cert rotation and the DNS entries.