NextDNS

seems nice. free limit is pretty generous. has a proper backend where you can blacklist things.

pretty much cloud based version of pi-hole from what i have been reading as i have not personally tried pi-hole.



this is the windows client lol.

started automatically just fine on boot. so solved the issue i was having with dnscrypt.

To verify the company... mozilla has added them as the second provider of DoH on Firefox.

Looks interesting, I pointed stubby on my OpenWRT router to NextDNS servers. It was all setup for DoT with CloudFlare earlier so I just had to the swap the endpoints.

Initial impression is really good. 🚀

looks like free version might not be enough. i have already done 156,260 queries this month. i started on december 18. and this is only on two devices. my computer and my phone.

it is in beta right now so completely free. once it goes paid... blocking features would stop working after the free limit is over which is currently set at 300,000 queries right now.

do tell how extensive the ad blocking is. i am not using that feature. how good it is. if it works well, i would put it on dad's phone.

Perhaps a local caching resolver can help reduce the hits to NextDNS? I currently have dnsmasq for local caching which is pointed to stubby which in turn talks to NextDNS.

Anyway I started only today, will keep the thread updated with my stats over the next couple of days/weeks.

I didn't enable the Ads and Trackers block list yet, for now just added the known BSNL ad injection domains in the blacklist. That worked as expected.

Windows is supposed to cache dns for 24 hours by default 😀

Which adblocker do you use on NextDNS to remove the ad placeholder as indicated in the screenshot. Have been using adguard. It works, but I hate these ugly placeholders.

Can you hide blank spaces used by blocked ads?
Unfortunately, this is not doable at the DNS level. You need a browser extension like ublock for that.

Click to expand...

So ran into an issue with NextDNS. My config is basically dnsmasq as a caching only dns resolver which forwards all non-cached queries to stubby which is configured for DoT to NextDNS.

The issue I noticed on two separate devices multiple times (an OpenWRT router and a CentOs 7 x86 minipc) is that stubby just goes to a hung state not responding to any queries. I had not enabled logging so not sure what exactly happens (I have since enabled logging), but restarting the stubby service resolves the problem.

I had a chat with NextDNS and they said stubby doesn't work so well with NextDNS for some reason. I've asked for their recommendation. I was on Stubby 0.2.4 on both devices when it showed the problem, I upgraded to 0.2.6 now. Let's see if the issue happens again.

Also to add, I had the exact same config for months with CloudFlare DNS (DoT) and never had an issue. This started after moving to NextDNS so its definitely some incompatibility with NextDNS. Anyway will keep an eye.

@Sushubh Sir, I have set up next dns on my router by using the provided IPv4 dns addresses. But it's still showing ads. I have also linked the Dynamic IP to NextDNS through dynamic dns. Please help.

you have to create an account and configure it from there. and use that account profile on your router. it does not block ads out of the box!

you might want to use adguard's dns service if you just need ad blocking!

i configured this on dad's phone today and it works fine. because it is on dns level... ad blocks are still there on web pages and apps but ads do not appear.

I have already done that. Read my edited post again.

also i doubt you would be able to block ads by just entering their ipv4 address in your router. i think to make it work, you would have to link your ip in your account. and update it every time it is changed. so adguard might be a better option for you!