Re:Decentralized DNS with the Handshake Naming System
by tynes on Tuesday August 06, 2019 @01:31PM
(#20627439)
Unfortunately the seeder peers aren't up right now, see here for a fresh peers list
Re:Decentralized DNS with the Handshake Naming System
by drexlspivey on Tuesday August 06, 2019 @04:43PM
(#20629422)
502 Bad Gateway
Re:Decentralized DNS with the Handshake Naming System
by ishanjain28 on Tuesday August 06, 2019 @04:49PM
(#20629474)
I tried it right after he suggested doing that.
Try this command, It contains a list of peers that were working few hours back. Maybe they are still online.
./hnsd -r 127.0.0.1:53 -s ajgkxfe47u6wwyvyh7qixbdddvjxcqbs2oxwr5attq45yj72s5pcs@54.201.46.33:13038,akudgzg2wntfjucsodyvz44h76qae7xrtuix6wc6fc22cx5jll6fe@165.227.52.206:13038,ajaqq7jwqrwixmvl64tzi3qfi7ynj3hmmtzmkyubtrljh4mwmh7ie@165.22.151.242:13038,ap77bve4acntajehkvqc33bvlsi27ka6l2xte4fhn2ghuwx44fsxc@18.236.58.201:13038
Compiled hnsd and tried to run it on local machine and an ec2 spot instance but it keeps failing to connect to it's (hardcoded?) peers.
I keep seeing this,
peer 354 (172.104.177.177:13038): failed connecting: connection refused peer 354 (172.104.177.177:13038): closing peer peer 354 (172.104.177.177:13038): closed peer peer 355 (139.162.183.168:13038): failed connecting: connection refused peer 355 (139.162.183.168:13038): closing peer peer 355 (139.162.183.168:13038): closed peer peer 353 (172.104.214.189:13038): failed connecting: connection refused peer 353 (172.104.214.189:13038): closing peer peer 353 (172.104.214.189:13038): closed peer peer 352 (173.255.209.126:13038): failed connecting: connection refused peer 352 (173.255.209.126:13038): closing peer peer 352 (173.255.209.126:13038): closed peer peer 357 (172.104.177.177:13038): failed connecting: connection refused peer 357 (172.104.177.177:13038): closing peer peer 357 (172.104.177.177:13038): closed peer peer 359 (139.162.183.168:13038): failed connecting: connection refused peer 359 (139.162.183.168:13038): closing peer peer 359 (139.162.183.168:13038): closed peer peer 358 (172.104.214.189:13038): failed connecting: connection refused peer 358 (172.104.214.189:13038): closing peer peer 358 (172.104.214.189:13038): closed peer peer 356 (173.255.209.126:13038): failed connecting: connection refused peer 356 (173.255.209.126:13038): closing peer peer 356 (173.255.209.126:13038): closed peer peer 363 (172.104.177.177:13038): failed connecting: connection refused peer 363 (172.104.177.177:13038): closing peer peer 363 (172.104.177.177:13038): closed peer peer 361 (139.162.183.168:13038): failed connecting: connection refused peer 361 (139.162.183.168:13038): closing peer peer 361 (139.162.183.168:13038): closed peer peer 362 (172.104.214.189:13038): failed connecting: connection refused peer 362 (172.104.214.189:13038): closing peer peer 362 (172.104.214.189:13038): closed peer peer 360 (173.255.209.126:13038): failed connecting: connection refused peer 360 (173.255.209.126:13038): closing peer peer 360 (173.255.209.126:13038): closed peer
Also, These IP address are either blocking ICMP ping messages or outright unreachable because ping fails to talk to them.