ctrld VS metadata

So when I discovered the Control D resolver, I thought I'd try to make this work instead. Getting it up and running in a Docker environment was easy. Repeating this on a Mikrotik router involved a little bit more learning on my part. The r/mikrotik community was instrumental in getting this up and running. As a thank-you for all the comments that helped me work this all out, I thought I'd write a full guide on how to replace the resolver built in to Router OS, with one by Control D.

With the help of others in r/mikrotik, I wrote a guide on how to run the ctrld resolver on a Mikrotik router. See here if you're interested.

If you can run Adguard for this, you can run ctrld directly on the same machine instead. It will do exactly what you wish, automatically. https://github.com/Control-D-Inc/ctrld

Please make an issue, and provide some details of your env here: https://github.com/Control-D-Inc/ctrld/issues

https://github.com/Control-D-Inc/ctrld Install this on your router and build a custom config to do what you’re looking for

If you want to use bleeding edge DNS protocols like DOQ, you can run this DNS proxy server: https://github.com/Control-D-Inc/ctrld

The listener IP for ctrld config will route your devices connections. So you need to point your devices to the IP where ctrld is running. https://github.com/Control-D-Inc/ctrld

I'm running a DNS utility directly on the pfsense firewall (Control D https://github.com/Control-D-Inc/ctrld/releases) and wanting to policy route the connections it makes through VPN gateways instead of WAN.

Check out ctrld: https://github.com/Control-D-Inc/ctrld

Which list is blocking archive.org? If "NextDNS Ads & Trackers Blocklist", probably some kind of mistake, write about it - https://github.com/nextdns/metadata/issues

You can find the NextDNS lists here: https://github.com/nextdns/metadata

You can always look at github. This is just the activity for their metadata repo: https://github.com/nextdns/metadata/commits/masterFeel free to check their other repos.

NextDNS gives you a whole bunch of 3rd party filters, maintained by random dudes in Github repos as a hobby. We support some of them too in the "3rd party filters" tab, however we don't encourage anyone to actually use them, as we have our own Native filters, that we've built up over the course of 5 years based on feedback for millions of Windscribe (our sister company) users. Our native filters are highly effective, and prone to much fewer false positives. We recommend you try them, you will be pleasantly surprised with how they perform. I guarantee you that you will spend 90% less time making whitelist rules for false blocks... or your money back :) "Native tracking protection" filters are all part of the IoT Filter. NextDNS has the individual toggles, which enforce this small set of rules. Out IoT filter enforces all of them, as well as 10x more things.

Here is the list: https://github.com/nextdns/metadata/blob/master/parentalcontrol/categories/video-streaming.json

Here's those native blocking lists from NextDNS: https://github.com/nextdns/metadata/tree/master/privacy/native

From https://github.com/nextdns/metadata/blob/master/privacy/blocklists/energized-ultimate.json the link used is https://block.energized.pro/ultimate/formats/domains.txt which currently contains nothing but comments.