-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNSCloak #3
Comments
This issue was automatically closed because it did not follow the issue template. We use the issue tracker exclusively for bug reports and feature additions that have been previously discussed. However, this issue appears to be a support request. Please use the discussion forums for support requests. |
Hi @knowyoutoo No at this point, and I think the developer has no plan to use this fork. DNSCloak doesn't support our extended protocols. It uses vanilla DNSCrypt, which means it supports a single-relay-based anonymization and no per-query relay randomization. |
But DNSCloak is an open source, and you may be able to build with this repo by yourself if you have an apple developer license (I don't have it...) |
Ok thanks. Makes sense. I was able to add some relays to cloak so I’ll play around with the configurations Sent from Proton Mail for iOS On Sat, Sep 9, 2023 at 10:40 AM, Jun Kurihara ***@***.***> wrote:
But DNSCloak is an open source, and you may be able to build with this repo by yourself if you have an apple developer license (I don't have it...)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Personally, I am using this fork by hosting this on cloud as a server with docker, and my phone and PCs connect though VPN with the server. This is similar to DNSCloak that uses (pseudo) VPN to realize split DNS, mine uses true VPN although. |
Any idea if DNSCloak will support this? Can the additional configuration fields be added into the dnscrypt-proxy.toml? If so, I imagine they would be able to
The text was updated successfully, but these errors were encountered: