You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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: