Thanks for the explanation. I have made a few changes for the next version that should help:
1) I have added /sockopen -46 switches which work in the same way as /server and /dns.
2) I have made /sockopen check the bind address and, if -46 are not specified, it will base its DNS resolution on whether the bind address is ipv4/ipv6. If no bind address is specified, it will be based on the server/global ipv4/ipv6 setting as before.
3) In previous versions, if a /server -46 switch was not specified but you specified an ipv4/ipv6 address, /server remained neutral and used the global ipv4/ipv6 setting. In the next version, if -46 is not specified, /server will base its ipv4/ipv6 context on the IP address type. This will affect the context of /dns, /sockopen, etc.
