Hi there @bitbeans,
I just updated to the latest version of Simple DNSCrypt, v0.5.4, and it appears to have removed features which was present in v0.4.3, such as service IP and port and the secondary service as stated in #302.


However, this meens that the listen address can not be set from the application any more. We used to run DNSCrypt in a domain environment and the listening IP/port was set to 127.0.0.2:53, which was then accessed by Microsoft DNS server as the forwarder. (as shown above)
-
So, could you bring back the listening IP section in the new versions of Simple DNSCrypt? I just updated because it was marked as critical.
-
In the previous versions of SimpleDNSCrypt, we could set "listen_addresses" manually from the UI, with the value set to 127.0.0.1:5353 or 127.0.0.2:53 for example. Now, since I can't access it from the app, I need to manually edit dnscrypt-proxy.toml with the ip:port to listen to.
Hi there @bitbeans,
I just updated to the latest version of Simple DNSCrypt, v0.5.4, and it appears to have removed features which was present in v0.4.3, such as service IP and port and the secondary service as stated in #302.
However, this meens that the listen address can not be set from the application any more. We used to run DNSCrypt in a domain environment and the listening IP/port was set to
127.0.0.2:53, which was then accessed by Microsoft DNS server as the forwarder. (as shown above)So, could you bring back the listening IP section in the new versions of Simple DNSCrypt? I just updated because it was marked as critical.
In the previous versions of SimpleDNSCrypt, we could set "
listen_addresses" manually from the UI, with the value set to127.0.0.1:5353or127.0.0.2:53for example. Now, since I can't access it from the app, I need to manually editdnscrypt-proxy.tomlwith the ip:port to listen to.