summaryrefslogtreecommitdiff
path: root/ca/22844dce050b4c40add7c5dfdfd315c2378c09
blob: aee58f44459c02f3b740ab955763b352ef3ca63b (plain)
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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gcbd-bitcoin-development@m.gmane.org>)
	id 1WlcyA-0000Dh-FW for bitcoin-development@lists.sourceforge.net;
	Sat, 17 May 2014 11:40:02 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of m.gmane.org
	designates 80.91.229.3 as permitted sender)
	client-ip=80.91.229.3;
	envelope-from=gcbd-bitcoin-development@m.gmane.org;
	helo=plane.gmane.org; 
Received: from plane.gmane.org ([80.91.229.3])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1Wlcy6-0002hU-Mq
	for bitcoin-development@lists.sourceforge.net;
	Sat, 17 May 2014 11:40:02 +0000
Received: from list by plane.gmane.org with local (Exim 4.69)
	(envelope-from <gcbd-bitcoin-development@m.gmane.org>)
	id 1Wlcxz-0004OF-IK for bitcoin-development@lists.sourceforge.net;
	Sat, 17 May 2014 13:39:51 +0200
Received: from e179039129.adsl.alicedsl.de ([85.179.39.129])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00 for <bitcoin-development@lists.sourceforge.net>;
	Sat, 17 May 2014 13:39:51 +0200
Received: from andreas by e179039129.adsl.alicedsl.de with local (Gmexim 0.1
	(Debian)) id 1AlnuQ-0007hv-00
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 17 May 2014 13:39:51 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: bitcoin-development@lists.sourceforge.net
From: Andreas Schildbach <andreas@schildbach.de>
Date: Sat, 17 May 2014 13:39:40 +0200
Message-ID: <ll7hps$8gs$1@ger.gmane.org>
References: <ll29m5$r6c$1@ger.gmane.org>
	<ll5ems$6pt$1@ger.gmane.org>	<09E70F88-DA1C-4E3F-9342-547FB8794EAB@heliacal.net>	<CALDj+BZrn6TBjdVjGkc293SLAAcqzni+-7daFpZAq5gSaL1cKw@mail.gmail.com>	<CAJHLa0OaAKTLR2hL6kReBFcD6FoXYV9AoqMbn0WwqYgtTNtQKw@mail.gmail.com>
	<CALDj+BY2jEL6-NwGdrh3wdcmjW_7tEDDxmyiP6woOxCg8bMQKw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: e179039129.adsl.alicedsl.de
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.5.0
In-Reply-To: <CALDj+BY2jEL6-NwGdrh3wdcmjW_7tEDDxmyiP6woOxCg8bMQKw@mail.gmail.com>
X-Enigmail-Version: 1.5.2
X-Spam-Score: -1.1 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [80.91.229.3 listed in list.dnswl.org]
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_HELO_PASS          SPF: HELO matches SPF record
	1.1 DKIM_ADSP_ALL          No valid author signature,
	domain signs all mail
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
X-Headers-End: 1Wlcy6-0002hU-Mq
Subject: Re: [Bitcoin-development] DNS seeds unstable
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: Sat, 17 May 2014 11:40:02 -0000

I think the best way to contribute to the infrastructure is actually
what we're doing: Test the current infrastructure and point out where it
is not working. Trying to find solutions for problems.

There is nothing gained by throwing additional hardware at a problem if
the problem itself isn't understood well.


On 05/17/2014 02:58 AM, Alex Kotenko wrote:
> Ok, what do I need to do? How do I host a testnet seed myself? 
> 
> Best regards, 
> Alex Kotenko
> 
> 
> 2014-05-16 23:02 GMT+01:00 Jeff Garzik <jgarzik@bitpay.com
> <mailto:jgarzik@bitpay.com>>:
> 
>     There are only two testnet seeds listed in bitcoind, and one of them
>     returns SERVFAIL (testnet-seed.bitcoin.petertodd.org
>     <http://testnet-seed.bitcoin.petertodd.org>) and the other
>     just returns one A record (testnet-seed.bluematt.me
>     <http://testnet-seed.bluematt.me>).  No idea what
>     seeds bitcoinj uses.
> 
>     If you are going to depend on testnet, especially for an important
>     demo... contribute to the infrastructure!  This stuff doesn't just fix
>     itself for free.