Follow the example to the letter and what you are trying to do should work. Any devices you set to the custom address will skip dns crypt and diversion. Since this is a diversion guide it is more appropriate that you move this to the diversion thread. Note they will not be able to skip diversion and still use dns crypt since they both pass through dnsmasq and the router itself. You will have to assign clients to a separate dns address altogether.
He wants DNSCrypt-Proxy to listen on the LAN as well, so he can bypass Diversion for some clients.
If you have directions for that you are welcome to share your methods. As far as it is setup now both dnscrypt proxy and diversion are handed off to dnsmasq.
I thought it would involve a change to listen_addresses to add a LAN IP like the Pixelserv IP on port 53. But I'm not that familiar with the rest of dnscrypt-proxy to be certain.
I am sure he could make a custom listen address for what he is trying to do, the down side is dnscrypt-proxy caching is disabled since it is handed to dnsmasq as well, so you may be taking a performance hit to those devices. Alternatively I recommend enabling diversions alternative block list and choosing a tiny custom blocklist, this will allow custom defined devices to use dnscrypt without taking any performance hit and prevent devices from being heavily impacted from diversion blocking.
So will something like this work...
You should try the method I mentioned instead of trying to manipulate dnscrypt proxy potentially making your internet unusable.
You could use a simple tiny list like this one
First you have to enable fast switch, then you pick a custom list for it, then you enable alternative block list and assign an unused ip address to it, then you add that Ip to custom 1 on dnsfilter and assign a filter for each device you want to use it.
I appreciate your feedback. Keep me updated on how well it works. I highly encourage the use of Diversions features as @thelonelycoder has made it simple. He has streamlined everything to be user friendly and easy to use. DNSMASQ (through diversion) is your most flexible means of taking care of this issue.
Guys don't update to this too soon. There is a memory leak and the binaries are not properly compiled for linux-arm and arm64 devices. I set the installer detectable dnscrypt-version back to 2.0.42 until the issue is resolved. I have opened an issue on dnscrypt-proxy 2's devs github. The issue involves dnscrypt-proxy 2 not properly binding to addresses.
Restore worked fine for me
