ACK https://github.com/bitcoin/bitcoin/blob/master/doc/dnsseed-policy.md
I'm willing to keep it up and running at least throughout 2018, unless something bad happens.
Same setup as #11917, but with a dedicated instance.
[net] add seed.bitcoin.sprovoost.nl to DNS seeds #11962
pull Sjors wants to merge 1 commits into bitcoin:master from Sjors:dns-seed-sjors changing 1 files +1 −0-
Sjors commented at 6:49 PM on December 20, 2017: member
-
jonasschnelli commented at 7:03 PM on December 20, 2017: contributor
Tested ACK ab8b18342d9d08d7eab8c64a5b1802150ebb9e95.
Domain is linked to http://www.uroulette.com (not sure if that is good or bad. :))Default SSH port is 22 (though I don't want to criticise your security setup)
Sjors is a relatively new contributor, first issue 2017-09-06 (#11219) PR opened 2017-09-26 (#11219), though, he is pretty active. He is active on Github since 2008.
-
Sjors commented at 7:16 PM on December 20, 2017: member
That's interesting... I've never heard of uroulette.com (I know, that's what they all say); what makes you believe they are linked?
Criticism of my security setup is certainly welcome. I configured EC2 to only allow inbound SSH from a single IP. I'm surprised that still leaves a trace for you to see that the port is open.
-
jonasschnelli commented at 7:24 PM on December 20, 2017: contributor
Oh ... I think my test was wrong. I guess it connected to one of the IPs from the seeder response.
curl -v seed.bitcoin.sprovoost.nl * Rebuilt URL to: seed.bitcoin.sprovoost.nl/ * Trying 144.76.99.209... * TCP_NODELAY set * Trying 2001::9d38:953c:2cba:3eb8:8e96:74d5... * TCP_NODELAY set * Immediate connect fail for 2001::9d38:953c:2cba:3eb8:8e96:74d5: No route to host * Trying 2001:470:8:7b3::17... * TCP_NODELAY set * Immediate connect fail for 2001:470:8:7b3::17: No route to host * Trying 2001:470:8:7b3::55... * TCP_NODELAY set * Immediate connect fail for 2001:470:8:7b3::55: No route to host * Trying 2001:470:1d:8a9::... * TCP_NODELAY set * Immediate connect fail for 2001:470:1d:8a9::: No route to host * Trying 2604:4500::a2:225:90ff:fe5c:f7f0... * TCP_NODELAY set * Immediate connect fail for 2604:4500::a2:225:90ff:fe5c:f7f0: No route to host * Trying 2001:470:1d:8a9::4... * TCP_NODELAY set * Immediate connect fail for 2001:470:1d:8a9::4: No route to host * Trying 2002:7169:8b2a::7169:8b2a... * TCP_NODELAY set * Immediate connect fail for 2002:7169:8b2a::7169:8b2a: No route to host * Trying 2001:470:1f07:124::3... * TCP_NODELAY set * Immediate connect fail for 2001:470:1f07:124::3: No route to host * Trying 2001:41d0:1004:3274::... * TCP_NODELAY set * Immediate connect fail for 2001:41d0:1004:3274::: No route to host * Trying 2001:470:1f10:776::2... * TCP_NODELAY set * Immediate connect fail for 2001:470:1f10:776::2: No route to host * Trying 2001:470:1f14:57a::2... * TCP_NODELAY set * Immediate connect fail for 2001:470:1f14:57a::2: No route to host * Trying 2001:470:1f15:1b95:2c3e:8a9a:24e1:7084... * TCP_NODELAY set * Immediate connect fail for 2001:470:1f15:1b95:2c3e:8a9a:24e1:7084: No route to host * Trying 2001:200::8801:5054:ff:fe32:e5be... * TCP_NODELAY set * Immediate connect fail for 2001:200::8801:5054:ff:fe32:e5be: No route to host * Connection failed * connect to 144.76.99.209 port 80 failed: Connection refused * Trying 97.107.131.168... * TCP_NODELAY set * Connected to seed.bitcoin.sprovoost.nl (97.107.131.168) port 80 (#0) > GET / HTTP/1.1 > Host: seed.bitcoin.sprovoost.nl > User-Agent: curl/7.54.0 > Accept: */* > < HTTP/1.1 302 Found < Date: Wed, 20 Dec 2017 19:22:08 GMT < Server: Apache/2.4.7 (Ubuntu) < X-Powered-By: PHP/5.5.9-1ubuntu4.22 < Location: http://www.uroulette.com/visit/utvtw < Content-Length: 0 < Content-Type: text/html -
Sjors commented at 7:53 PM on December 20, 2017: member
curlwill show you a random website every time you try. Probably because it encounters an A record and just follows the trail, to whatever web server happens to be running on the node machine.nmapgets tripped up in a similar way. - fanquake added the label P2P on Dec 21, 2017
-
ghost commented at 2:48 PM on January 4, 2018: none
- unknown approved
-
fanquake commented at 1:33 PM on January 29, 2018: member
Needs a rebase.
-
[net] add seed.bitcoin.sprovoost.nl to DNS seeds ffcc687c55
- Sjors force-pushed on Jan 29, 2018
-
Sjors commented at 6:11 PM on January 29, 2018: member
Rebased
-
laanwj commented at 8:49 AM on February 17, 2018: member
I've checked that the DNS seed returns connectable hosts.
Criticism of my security setup is certainly
FWIW I was not able to find an open SSH port on port 22, nor any other open low/well-known port. Due to this, nmap was unable to even do OS detection.
-
-
sipa commented at 5:05 PM on March 22, 2018: member
ACK
-
cdecker commented at 3:41 PM on March 26, 2018: contributor
ACK
Tested the quality of the results returned by the seed 3 times. The results show how many of the returned nodes are reachable: 15/22, 20/22, and 21/22. Pretty much average with the other seeds.
- laanwj merged this on Mar 26, 2018
- laanwj closed this on Mar 26, 2018
- laanwj referenced this in commit 0a018431c4 on Mar 26, 2018
- Sjors deleted the branch on Mar 26, 2018
- MarcoFalke locked this on Sep 8, 2021
