It seems there's DNS solving issue since ver 2.76/2.77

[hyyz17200]

I kept using 2.74 for a long time. When I updated it to 2.77 also any newer version, I could not connect to the pool. There was a red line saying: "Failed: Connection closed."

I have a unique port forwarding for my rig because I stayed in China and want to hide my traffic into a v2ray proxy.

I was not using an internal IP as 127.0.0.1. Instead, I changed my router DNS setting and host "asia1.ethermine.org" to "127.0.0.1" and used another port, 20341, to identify if the traffic was proxied.

So, I set "asia1.ethermine.org:20341" to go. And it was all OK with 2.74.

I monitored my proxy, and since 2.77, there's no new incoming handshake. So I believe 2.77 uses DoH to get the real pool IP and fails with the 20341 port, which is not correct.

I read all changelog, and I did set secure DNS to 0. Nothing helped.

I changed my pool setting to "127.0.0.1:20341" now, and it works now. I was doing it using a domain host because some of my other rigs use other miners, which will check the SNI of HTTPS. 127.0.0.1 won't work.

Sorry for telling a bizarre usage and long story. That's how it is, and I think the DNS is forced to DoH. It's a bug.

Thanks!