Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.212.172 as permitted sender)
	client-ip=209.85.212.172; envelope-from=jgarzik@bitpay.com;
	helo=mail-wi0-f172.google.com; 
MIME-Version: 1.0
In-Reply-To: <ll29m5$r6c$1@ger.gmane.org>
References: <ll29m5$r6c$1@ger.gmane.org>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 15 May 2014 13:41:31 -0400
Message-ID: <CAJHLa0Pb3gPFiFVwTowRCZ1duudvXpD_VbE6viJXHb4+3iqKKQ@mail.gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds unstable
Precedence: list

On Thu, May 15, 2014 at 7:50 AM, Andreas Schildbach
<andreas@schildbach.de> wrote:
> I'm bringing this issue up again. The current Bitcoin DNS seed
> infrastructure is unstable. I assume this is because of we're using a
> custom DNS implementation which is not 100% compatible. There have been
> bugs in the past, like a case sensitive match for the domain name.

While I agree that the problem seeds should be fixed, it also sounds
like a problem with bitcoinj / other layers, if a malfunctioning seed
is a problem for your app.

Seeds are fundamentally a backup for peer exchange.  You are going to
run into problems if you rely 100% on seeds, always.

Further, there are multiple seeds so that we are not impacted if a
couple seeds malfunction or die.  All bitcoin apps must take this into
account.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/