These was one of the fastest DoH services for pipelined queries over single TCP connection
IME, it was much faster than Quad9 for this purpose
First Mullvad shuts down its Google search proxy
Now its DoH service
What's next
Shutting down our public encrypted DNS
11–20 of 234 posts
Re: Shutting down our public encrypted DNS
#12Does anyone know of good alternatives that also block ads? Seems Quad9 doesn't.
Re: Shutting down our public encrypted DNS
#13Does anyone know of good alternatives that also block ads? Seems Quad9 doesn't.
nextdns.io might be an option
https://adguard-dns.io/kb/general/dns-providers/ have a list of options that some of them have ad blocker
Re: Shutting down our public encrypted DNS
#14Their founder supports Nazis.
Re: Shutting down our public encrypted DNS
#15Earlier quoted context omitted.
On the Quad9 website: >Since Quad9 already performs DNSSEC validation, DNSSEC being enabled in the forwarder will cause a duplication of the DNSSEC process, significantly reducing performance and potentially causing false BOGUS responses. This sounds dodgy. Surely that means Quad9 can poison my DNS?
Not if Quad9 is using DNSSEC, no. What's the specific threat you're envisioning? If it involves Quad9 themselves being malicious, what would DNSSEC on the forwarding prevent? This page explains how all of this works in detail: https://quad9.net/news/blog/quad9-enables-dnssec-on-all-serv...
DNSSEC validation on your forwarder would prevent a maliciously modified record from Quad9 (or others) from being accepted locally - i.e. "Quad9 can poison my DNS".
I've always been of two minds on this. On one hand, that concern is beyond any reasonable level of security/performance/reliability tradeoff for most any user. At the same time, it is a bit of a shame DNS doesn't have a more scalable & performant approach to security which can just always be done without having to consider it a tradeoff, however minor in practice.
Re: Shutting down our public encrypted DNS
#16Does anyone know of good alternatives that also block ads? Seems Quad9 doesn't.
NextDNS https://nextdns.io/
Re: Shutting down our public encrypted DNS
#17Does anyone know of good alternatives that also block ads? Seems Quad9 doesn't.
Re: Shutting down our public encrypted DNS
#18I'm always wondering whether those centralized privacy services are not the easiest first target for three-letter-agencies to infiltrate to gain access to the most relevant users to track - and what currently would prevent them from doing so if they haven't already ? Maybe, as with the case of many TOR nodes , they might be running them.
Re: Shutting down our public encrypted DNS
#19Does anyone know of good alternatives that also block ads? Seems Quad9 doesn't.
What about Cloudflare’s public DNS? https://developers.cloudflare.com/1.1.1.1/setup/#1111-for-fa...
1.1.1.2
1.0.0.2
2606:4700:4700::1112
2606:4700:4700::1002Re: Shutting down our public encrypted DNS
#20>We want a public service to be available. Going forward, we will support Quad9 instead of running it ourselves. Running a privacy-focused public DNS service is a highly specialized undertaking, and the Quad9 Foundation is the undisputed leader in the field. Rather than duplicating their efforts to achieve only part of what they do, we're putting those resources toward financially supporting Quad9 instead. Brilliant.
Quad9 doesn't have an adblocking DNS service though, so it's not really a replacement.
This is a very important detail. Adblock in 2026 is necessary and DNS will transparently do a lot of that work for you. It isn't just about lightning fast lookups and five-nines uptime anymore.