DNS support on lotus-workers have been dropped

[piknikSteven2021]

Checklist

• [X] This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• [X] I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• [X] I am running the Latest release, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
• [X] I did not make any code changes to lotus.

Lotus component

• [ ] lotus daemon - chain sync
• [ ] lotus fvm/fevm - Lotus FVM and FEVM interactions
• [X] lotus miner/worker - sealing
• [ ] lotus miner - proving(WindowPoSt/WinningPoSt)
• [ ] lotus JSON-RPC API
• [ ] lotus message management (mpool)
• [ ] Other

Lotus Version

root@sp-71c3:/home/lotus# lotus-worker --version
lotus-worker version 1.25.0+mainnet+git.7e6b20cd9

Repro Steps

1. Export or set environmental variable as miner admin api-info with dns4/<dns name> rather than IPv4.
2. Start the worker.

Describe the Bug

It appears that DNS support for miner API on the lotus-worker has been removed (though I don't think it appears DNS support was intended). On several of my workers after upgrading to v1.25.0 - I noticed the following error:

2023-11-29T02:33:39.966Z        INFO    main    lotus-worker/main.go:556        Opening local storage; connecting to master
2023-11-29T02:33:39.971Z        WARN    main    lotus-worker/main.go:116        dial tcp :2345: connect: connection refused

Host nslookup of the DNS names resolved with zero issues - the issues were prevalent only on the lotus-worker itself. It appears to me that the changes made to support IPv6 has ended up dropping DNS unintentionally. In this commit, at line 750-751 you can see that lotus-worker would just parse the miner API to get the address and port. But they were removed in favor of 765-774 and 779-786.

Logging Information

2023-11-29T02:33:39.966Z        INFO    main    lotus-worker/main.go:556        Opening local storage; connecting to master
2023-11-29T02:33:39.971Z        WARN    main    lotus-worker/main.go:116        dial tcp :2345: connect: connection refused

[piknikSteven2021]

While I don't pretend to know Go and how to fix this, I can point to this line as to why DNS is not working anymore.

[johansealstorage]

I'm experiencing the same issue where this change broke my docker compose and kubernetes deployments where I was using DNS to automatically resolve and connect form workers to the miner.