A SOCKS Reply Is Not a DNS Lookup Result
Distinguish proxy-side hostname use from a DNS-query API and interpret a SOCKS CONNECT bound address correctly.
Asking a SOCKS proxy to connect to a hostname is not the same as asking it to return that hostname's DNS records.
The proxy can resolve the name as part of establishing the requested connection. It can also pass the task to another appropriate upstream. The client receives a SOCKS reply describing the connection result, not a general DNS response.
For CONNECT, the reply's bound address and port describe the server-side binding defined by the protocol. Do not treat BND.ADDR as a promised copy of the destination's resolved IP.
If the application only needs the connection, it can use the resulting stream without knowing which destination address the proxy selected. If it needs DNS data itself, choose an actual DNS-capable interface with the intended resolver location and policy.
That distinction also prevents a misleading IP check: the proxy's bound address, a destination IP, and the website-facing public exit are different values. One should not be labeled as another merely because it appeared in the same handshake.