1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1TyGon-0003na-3Q
for bitcoin-development@lists.sourceforge.net;
Thu, 24 Jan 2013 07:01:49 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.101 as permitted sender)
client-ip=62.13.149.101; envelope-from=pete@petertodd.org;
helo=outmail149101.authsmtp.com;
Received: from outmail149101.authsmtp.com ([62.13.149.101])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1TyGol-0008G0-2n for bitcoin-development@lists.sourceforge.net;
Thu, 24 Jan 2013 07:01:48 +0000
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
by punt5.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id
r0O71cNK066596; Thu, 24 Jan 2013 07:01:38 GMT
Received: from savin (206-248-185-35.dsl.teksavvy.com [206.248.185.35])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r0O71XFk052616
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Thu, 24 Jan 2013 07:01:36 GMT
Date: Thu, 24 Jan 2013 02:01:03 -0500
From: Peter Todd <pete@petertodd.org>
To: bitcoin-development@lists.sourceforge.net
Message-ID: <20130124070103.GA30820@savin>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: e52eba1c-65f3-11e2-b10b-0025903375e2
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAYUElQaAgsB AmUbW1NeUFx7WmQ7 aQpXcwdZalRPVwB0
U01WR1pVCwQmQxx+ AR92JEJycgdAeXg+ Y05gWz4OWUYvJxd8
EVNSEDsFeGZhPWIC AkFYJR5UcAFPdx9G aVd6AXFDBTBEIiQ1
A0cfGQt5JjhSJExc
X-Authentic-SMTP: 61633532353630.1019:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 206.248.185.35/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1TyGol-0008G0-2n
Subject: [Bitcoin-development] Testnet DNS seed
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 07:01:49 -0000
--HcAYCG3uE/tztfnV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
I setup a testnet DNS seed using Pieter Wuille's bitcoin-seeder, with
some simple modifications for testnet. It's at
testnet-seed.bitcoin.petertodd.org I also created
static-testnet-seed.bitcoin.petertodd.org which currently has a single A
record pointing to a testnet node I'm running to bootstrap the seeder
itself.
Everything is running on a dedicated Amazon EC2 micro instance. Just
IPv4 is supported right now as EC2 doesn't support IPv6; even tunnels
are broken. I also haven't setup tor yet. I can do both if there is
demand.
I guess the next step is to create a new strTestNetDNSSeed in the
satoshi client, although it'd be better if at least one more person had
a testnet seed to include in the list. Probably best to leave IRC
enabled too.
Also, FWIW, it looks like the pnSeed list is way out of date...
Pieter: Have you written any start/stop/monitoring scripts for the
seeder? My mods are at git://github.com/petertodd/bitcoin-seeder.git in
the "testnet" branch. I'll send you a pull request once it's had some
testing.
--=20
'peter'[:-1]@petertodd.org
--HcAYCG3uE/tztfnV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJRANwuAAoJEH+rEUJn5PoEcwUIAIZ7GFE6WT7py9NXuMtI0B4M
HcX5cO/7phBMQ7Y78LoD4LxhZMlgeiTxvm9ik88dmRQs5piP6b9hEuNCac++vqbC
xhCyaW+AaWjqEfYgxUTt2BuOmqy2nm5m2sdHG2LsotnMquWF65EQA/KKFD9U7VxI
uDhU0qHJQRRn1MfgS3D4FSk248i5IA1QncM8OzVZ/c5oANR+eI0ouB/O5RKEXrou
iT5nzllJQDi+NQtwo45T8ECMqcYWg7bt+4qX+SfwhkhQVEzwG4aEgD6EVisFUriZ
zLk8IVMWTZhU4dPrJ+ytCMOPya0iq0ixcNV/vnB9Aca133urVC2xe/BKqJ/abaY=
=x9XO
-----END PGP SIGNATURE-----
--HcAYCG3uE/tztfnV--
|
