Received-SPF: pass (sog-mx-1.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; 
To: bitcoin-development@lists.sourceforge.net
From: Andreas Schildbach <andreas@schildbach.de>
Date: Sun, 25 May 2014 21:12:10 +0200
Message-ID: <lltfaa$2lv$1@ger.gmane.org>
References: <20140523221726.GA30143@petertodd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.5.0
In-Reply-To: <20140523221726.GA30143@petertodd.org>
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up
	again
Precedence: list

Thanks for looking at the issue.

Unfortunately, it still fails for me:

$ nslookup testnet-seed.bitcoin.petertodd.org
Server:		127.0.1.1
Address:	127.0.1.1#53

** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL

Like I said, can you look at the logfiles how the requests arrive?

What particular thing did you fix? It would be good to know for future
outages.


On 05/24/2014 12:17 AM, Peter Todd wrote:
> FWIW
> 
> That said, keep in mind the github discussion(1) that was had: if all
> the DNS seeds being down breaks your application, your application is
> broken and insecure. The only exception is initial startup, and even
> then you should have fallbacks such as hardcoded node lists and manual
> peer entry. If for some reason you really do need instant startup, run
> your own centralized high-availability/low-latency nodes; either way
> you're depending on a centralized resource.
> 
> 1) https://github.com/bitcoin/bitcoin/pull/4203