ctrld VS fritzconnection

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

And specifically for fritzbox, however, there are libraries like fritzconnection, that could be used to retrieve the client list and send client info.