target DNS gets resolved prior to proxy connect (MITM)
GlenDC opened this issue · comments
The MITM Proxy receives a resolved IP address of the target to connect to. This works for most providers but some providers seem to result in undesired behaviour such as wrong upstream proxy selection when going via the target IP address on connect instead of the actual DNS.
Currently one can hack around this — if your provider allows dynamic parts in the proxy url — by including socks5h somewhere in the url, as the MITM proxy Typescript code checks on this. It's however far from ideal.
Better would be to either make this opt-out or opt-in. So that at least we can disable it for the proxy providers that we know it causes issues for.
More info regarding the proxy provider. Apparently they do not allow by default to target IP addresses (for reasons), and as such this is why we get issues when using target addresses instead of DNS addresses.