dns seed connection error should not spam debug.log #7215

Running a testnet tor only node gives

$ grep -c testnet-seed.alex  ~/.bitcoin/testnet3/debug.log  
330628

$ tail ~/.bitcoin/testnet3/debug.log 
2015-12-15 13:33:57 ERROR: Proxy error: host unreachable
2015-12-15 13:33:58 SOCKS5 connecting testnet-seed.alexykot.me
2015-12-15 13:34:01 ERROR: Proxy error: host unreachable
2015-12-15 13:34:01 SOCKS5 connecting testnet-seed.alexykot.me
2015-12-15 13:34:21 ERROR: Error reading proxy response
2015-12-15 13:34:22 SOCKS5 connecting testnet-seed.alexykot.me
2015-12-15 13:34:23 ERROR: Proxy error: host unreachable
2015-12-15 13:34:23 SOCKS5 connecting testnet-seed.alexykot.me
2015-12-15 13:34:26 ERROR: Proxy error: host unreachable
2015-12-15 13:34:26 SOCKS5 connecting testnet-seed.alexykot.me

Other testnet seeds seem not to be affected. When I don't run tor only, the issue is not visible anymore.

The server seems to be down at least since april? Handing in a pull request to fix this in a minute.

@tnull Are you sure? I think I didn't get this error when I disabled tor-only

At least Google yielded some people complaining about it being offline. Dig also suggest that this domain is not resolved at all: https://toolbox.googleapps.com/apps/dig/#A/testnet-seed.alexykot.me

But maybe I'm too fast and some of the regular devs know more about it.

I guess the host or dns entry is down:

$ dig testnet-seed.alexykot.me 

; <<>> DiG 9.8.3-P1 <<>> testnet-seed.alexykot.me
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48899
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;testnet-seed.alexykot.me.  IN  A

Closing, #7216 has been merged. IMO, the log output is sufferable because a such problem should be rare, and it it appears, we should consider removing the seed or contacting the operator.