-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
[FEATURE] Custom DNS To Stop Leaks #207
Labels
Comments
Could you please add more context on "[...] using a socks 5 proxy [...] the hostname would be leaked.", @hbednar? |
What i am meaning is if you are using a socks5 proxy with just an ip, then all dns and other requests would be sent to that proxy, as expected. But, if you were using a socks5 proxy with a hostname then, that would need to be resolved using your default dns before you could connect to that proxy. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
If you are using a socks 5 proxy with hostnames then the hostname would be leaked.
Describe the solution you'd like
To stop this and also to have the option can you add support for custom DNS ideally over https or tls.
This could be done using kdig but, it would need knot-dnsutils installed.
Alternatively you could use dig.
kdig -d @8.8.8.8 +tls-ca +tls-host=dns.google.com example.com
dig @9.9.9.9 google.com +tls
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: