Bug #77924 | JDBC SOCKS should not perform local DNS resolution | ||
---|---|---|---|
Submitted: | 3 Aug 2015 23:09 | Modified: | 7 Apr 2022 22:02 |
Reporter: | David Phillips | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.1.35 | OS: | Any |
Assigned to: | Alexander Soklakov | CPU Architecture: | Any |
Tags: | jdbc, socks |
[3 Aug 2015 23:09]
David Phillips
[6 Jan 2022 7:01]
Vipul Goel
Hi Team, May I know when this issue will be fixed. Or is there a workaround. Please fix this soon it is affecting too much at our end. Thanks, Vipul goel
[7 Apr 2022 22:02]
Daniel So
Posted by developer: Added the following entry to the Connector/J 8.0.29 changelog: "A new connection property socksProxyRemoteDNS has been added, which, when set to true, makes the SocksProxySocketFactory execute its own connect() implementation that passes the unresolved InetSocketAddress of a MySQL Server host to the created proxy socket, instead of having the address resolved locally."