Serious Discussion DNS Providers for Home Users – Still Cloudflare/Quad9, or Did NextDNS/Control D Finally Win?

What DNS provider(s) do you force on your home network / PC?

  • Cloudflare 1.1.1.1 (or 1.1.1.2/3) – speed king

  • Quad9 – best free malware/phishing blocking

  • Google 8.8.8.8 – I don’t care, just works

  • NextDNS – worth the config time and (sometimes) the $20/year

  • Control D – NextDNS but better UI and free tier actually good

  • AdGuard DNS – most aggressive ad/tracker blocking for free

  • Mullvad DNS / DNSCrypt – paranoid zero-log gang

  • My ISP’s DNS – yes I’m that guy

  • Self-hosted (Pi-hole, AdGuard Home, Technitium, etc.)

  • Mix – different DNS per device/profile


Results are only viewable after voting.
ControlD uses a feed of domains registered daily.
They will not perform a real time whois on all domains, as this will be costly, unreliable and very slow.

The feeds come from a third-party supplier.

If the supplier has issues such as delays, technical problems, poor coverage and so on, ControlD inevitably fails at blocking NRD.

Cloudflare has much better partnerships than ControlD.

However, the standard 1.1.1.1 with malware blocking is the mediocrity itself.
 
You can use:
Thanks
ControlD uses a feed of domains registered daily.
They will not perform a real time whois on all domains, as this will be costly, unreliable and very slow.

The feeds come from a third-party supplier.

If the supplier has issues such as delays, technical problems, poor coverage and so on, ControlD inevitably fails at blocking NRD.

Cloudflare has much better partnerships than ControlD.

However, the standard 1.1.1.1 with malware blocking is the mediocrity itself.
This is very informative, thanks. I set up a free account to try Cloudflare Zero Trust, and it seems to offer more content and security filtering options than ControlD. However, ControlD has AI-based malware filtering and supports third-party blocklists from Hagezi. CFZT portal also includes network filtering and HTTP filtering settings but I'm not sure of their effectiveness.
 
You can use:
This test shows which DNS you're using, not if the DNS filtering is working.

If someone wants to test if their DNS filtering is working correctly, they can either visit a domain present in the blocklist one uses, or manually block some domain in the control panel and then try to visit it. If you can't access the website under blocked domain, then the filtering works. If you can still visit the website, then something went wrong.
 
Last edited:
This test shows which DNS you're using, not if the DNS filtering is working.

It shows that the request is sent properly to the DNS resolver. This method is recommended by Control D.
This method cannot show what Control D is doing with the request. The method posted by you also cannot be used to confirm if all aspects of filtering work well. This would require more comprehensive testing on URLs.
 
It shows that the request is sent properly to the DNS resolver. This method is recommended by Control D.
Actually, what these DNS leak testing sites do is fire up bunch of requests in order to find out which DNS resolvers resolved the query. The purpose of these sites is to show you if any requests were answered by DNS resolver that you didn't set or use.
The method posted by you also cannot be used to confirm if all aspects of filtering work well. This would require more comprehensive testing on URLs.
Correct method would be test all blocked domains, but it's hella lot of work and testing few random domains will do the job. Beside, you can always look at logs to see what was blocked and what not.
 
I just read this post by Andrew Morris:

gm linkedin! Hope everyone enjoyed the superbowl! It's just about as american as it gets. I didn't watch it because I haven't unpacked my TV yet. Instead, I spent the evening arguing with my… | Andrew Morris | 36 comments

For those who don't know him, he is the founder and chief architect of GreyNoise Intelligence, so he's no newcomer:

Why GreyNoise

I don't want to make any judgments without further information.;)
He just doesn't know how adblockers work so what he found is surprising to him.
I see that things have been clarified in the comments; one of which is from the AdGuard CTO.
 
He just doesn't know how adblockers work so what he found is surprising to him.
I see that things have been clarified in the comments; one of which is from the AdGuard CTO.
Exactly! He simply doesn't understand the concept of ad blocking and thinks everything can be done just by using DNS when it actually can't. Claims about AdGuard working from Russia are entirely wrong as large majority of their team was relocated from Russia; they don't even have servers there anymore let alone anything else. It's true that some of their products were developed by Russian company but from what I understand, they cut the ties and AdGuard is now developed independently. Their only connection with Russia is reseller they use to sell their products there, nothing else.

I suggest him not to look how uBlock Origin works; it also manipulates with DOM and injects scripts. It simply has to if you want it to block YouTube, Twitch and similar ads as well as get rid of annoying cookie prompts.

And yes, some of the code is closed source. AdGuard already answered why on PrivacyGuides and Reddit multiple times. Some libraries they use in their products are closed source and the license doesn't allow them to open source the code. If they did, they could end up being in trouble because they violated the license and could be sued. I think it's in their plans to develop something independently so they can open source the code in future.
 
Mullvad.jpg


Works for me, I can change things quickly. I think I'm moving into my twilight years :):):)
 
Claims about AdGuard working from Russia are entirely wrong as large majority of their team was relocated from Russia; they don't even have servers there anymore let alone anything else.
Servers and legal stuff is moved out of Russia you are right about that. Bit moving the majourity of theur dev team to Cyprus is questionable.

A while ago job listings were all in Russia. When you look at the address were they are located, it does not seem like a software development centre. The buiilding above with an entrance on the right (you can move to it with street view does not has AdGuard listed).

1774286688082.png


1774287058384.png
 
Last edited:
Servers and legal stuff is moved out of Russia you are right about that. Bit moving the majourity of theur dev team to Cyprus is questionable.

A while ago job listings were all in Russia. When you look at the address were they are located, it does not seem like a software development centre. The buiilding above with an entrance on the right (you can move to it with street view does not has AdGuard listed).

View attachment 296547

View attachment 296549
There was a whole debate on Privacy Guides forum about AdGuard; whether it can be trusted and Andrey Meshkov (AdGuard CTO & co-founder) explained everything and answered all of the questions, so I recommend you check this out.
 
I am not talking about trust, just simply stating that their HQ location does not seem to be a development centre and the only open job listings for AdGuard are in Moscow.

The link you provided raises more questions than it answers, because the CEO suggest that the people contracted in Russia are not developers (AI found job openings typical for web development in Moscow like full stack developer and android developer).
andrey Meshkov said:
Most of the company’s employees relocated in 2022. There were two big waves, one in March 2022 and the other in September 2022. That said, we still have a bunch of contractors that reside in Russia, including part of the support service, a couple of QA engineers, and part of the content management team

What raises trust levels for AdGuard is that they are making their software open source (but I think they are bending the truth a little by stating that the development is done outside Russia and only support and marketing roles are left behind in Moscow).
 
Last edited: