Axe on IPv6 network prefers ipv4

[0xf0xx0]

Describe the bug
An axe running on an ipv6 enabled network should prefer ipv6 when resolving hosts, but instead prefers ipv4. this can be seen with ckpool and atlaspool.

To Reproduce
Steps to reproduce the behavior:

1. configure an ipv6-enabled pool
2. open the logs
3. restart your axe
4. when it resolves the domain, itll be the ipv4

Expected behavior
ipv6 should be preferred when available.

Hardware:

• ESP-Miner FW version: master
• Pool URL, Port: solo.atlaspool.io:4333

Additional context

I (18525) stratum_task: Resolved solo.atlaspool.io:4333 → 166.117.239.148
I (18526) stratum_task: Connecting to: stratum+tcp://solo.atlaspool.io:4333 (166.117.239.148)

[mutatrum]

I'm not sure if expected behavior is what we want. Maybe it should be a use choice?

[0xf0xx0]

maybe default ipv6-preferred with an option to prefer ipv4? the expectation on ipv6 enabled networks is everything that supports ipv6 will use it, and ipv4 is the fallback.

[WantClue]

This would be accaptable I guess. We always should preffer ipv4 imo for the sake of a clean process. But indeed if the bitaxe itself can optain an ipv6 address this should be proof that the network utilizes ipv6 and then we can prefer ipv6

[WantClue]

The issue here is that IPv6 is required on the entire chain from the bitaxe to the pool. If anything in between does not meet it it will prefer ipv4. Also for the testing of ipv6 i used solo6.ckpool becuase this is a straight ipv6 DNS record and I don't know if this is the case for atlaspool with one record for everything so ipv4 will very likely be used there.

[WantClue]

A potential solution would be to let the user decide what should be preferred but TBH i don't wanna write that :D