Don't use Cloudflare by default

[ameshkov]

Cloudflare DOH might be problematic because of the EDNS padding extension they add.

See #1110 (comment) for instance. Also, I suppose that #1109 was also caused by the very same thing.

Let's change it to Quad9 instead: https://dns.quad9.net/dns-query

Also, don't forget to change the text and examples: https://uploads.adguard.com/up04_1kfna_AdGuard_Home.png

Q&A

• Q: Why not Cloudflare DoT?

• A: DoH is less likely to be blocked on the ISP level.

• Q: Why not Google DNS?

• A: While I have nothing against it, people tend to hate everything made by Google

• Q: Why not AdGuard DNS?

• A: AdGuard DNS blocks ad trackers by itself. AdGuard Home users should decide what to block by themselves, they don't need a resolver to do it for them. Also, we don't have as many servers as Quad/Google/Cloudflare do so routing might be worse.

• Q: Why not any other resolver?

• A: Other public resolvers are considerably smaller than Cloudflare.

[ameshkov]

Well, we can consider using AdGuard DNS by default in one ane only case -- if we add an endpoint that does no ad & tracking filtering. But it kinda defeats the purpose, the idea of AdGuard DNS is to block this stuff:)

[ibksturm]

spasiba siem ot agh 0.99.1 :)

[ghost]

Just wanted to add that Quad is a great choice in my opinion. Non-profits (don’t really care if one of the founders is a government organization) are great as defaults when we are talking about critical web services such as DNS 🚀

[hoshsadiq]

Very happy with the new choice

AdGuard Home users should decide what to block by themselves, they don't need a resolver to do it for them

Just an FYI, just for completeness, Quad9 also blocks entries, specifically it blocks malicious domains.