Last active
February 14, 2018 21:08
-
-
Save leto/23346cc7ac246eb773e03dae8a75fa0d to your computer and use it in GitHub Desktop.
zdash.suprnova.cc DNS seed problems
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 147.135.220.159 goes to btcz.suprnova.cc | |
| The above happens because zdash.suprnova.cc is listed as a DNS seed of Hush, and something changed about 2 weeks ago which made it | |
| start returns BitcoinZ nodes instead of Hush nodes. | |
| I see a BTCZ DNS seeder magic string in my debug.log (everybody does) which should never happen: | |
| 2018-02-12 18:33:41 receive version message: /bitcoinzseeder:0.01/: version 770002, blocks=0, us=52.43.68.44:8888, peer=5915 | |
| 2018-02-12 18:34:29 receive version message: /bitcoinzseeder:0.01/: version 770002, blocks=0, us=52.43.68.44:8888, peer=5916 | |
| 2018-02-12 18:36:29 receive version message: /bitcoinzseeder:0.01/: version 770002, blocks=0, us=52.43.68.44:8888, peer=5917 | |
| 2018-02-12 18:41:19 receive version message: /bitcoinzseeder:0.01/: version 770002, blocks=0, us=52.43.68.44:8888, peer=5920 | |
| which then causes every BTCZ node to be banned: | |
| 2018-02-12 18:24:11 Misbehaving: 73.208.123.145:60337 (0 -> 100) BAN THRESHOLD EXCEEDED | |
| 2018-02-12 18:26:55 Misbehaving: 85.195.228.122:64631 (0 -> 100) BAN THRESHOLD EXCEEDED | |
| 2018-02-12 18:36:39 Misbehaving: 94.188.54.72:56249 (0 -> 100) BAN THRESHOLD EXCEEDED | |
| 2018-02-12 18:46:08 Misbehaving: 188.0.169.3:2054 (0 -> 100) BAN THRESHOLD EXCEEDED | |
| 2018-02-12 18:46:49 Misbehaving: 77.220.130.136:51326 (0 -> 100) BAN THRESHOLD EXCEEDED | |
| 2018-02-12 18:48:44 Misbehaving: 46.34.192.222:50305 (0 -> 100) BAN THRESHOLD EXCEEDED | |
| 2018-02-12 18:52:55 Misbehaving: 220.76.116.226:64059 (0 -> 100) BAN THRESHOLD EXCEEDED | |
| 2018-02-12 18:56:24 Misbehaving: 173.76.182.111:60907 (0 -> 100) BAN THRESHOLD EXCEEDED | |
| This is a massive waste of bandwidth for all involved, including your pool. | |
| It's impossible to run a DNS Seed for 2 coins on 1 IP, and it seems that your IP became a BTCZ dns seed a few weeks ago. | |
| This has caused most people who want to sync a fresh Hush node to be unable to sync, since our other 2 DNS seeds are down currently. | |
BitcoinZ is also seeing this in its debug logs:
2018-02-13 14:43:15 receive version message: /zcashseeder:0.01/: version 170002, blocks=0, us=34.211.79.94:1989, peer=4686
2018-02-13 14:43:47 receive version message: /bitcoinzseeder:0.01/: version 770002, blocks=0, us=34.211.79.94:1989, peer=4687
2018-02-13 14:46:49 receive version message: /hushseeder:0.01/: version 170002, blocks=0, us=34.211.79.94:1989, peer=4688
2018-02-10 20:59:04 receive version message: /MagicBean:1.0.81/: version 170002, blocks=1, us=34.211.79.94:1989, peer=4743
2018-02-10 22:39:13 receive version message: /MagicBean:1.0.81/: version 170002, blocks=0, us=34.211.79.94:1989, peer=4827
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey guys, just found that the ZCL dev team issued this response to Cryptopia regarding a similar problem: https://twitter.com/ZclassicCoin/status/962468944287281152.
Hope this helps!