From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WkzfK-0002kO-TN for bitcoin-development@lists.sourceforge.net; Thu, 15 May 2014 17:41:58 +0000 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; Received: from mail-wi0-f172.google.com ([209.85.212.172]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WkzfJ-0000iQ-QU for bitcoin-development@lists.sourceforge.net; Thu, 15 May 2014 17:41:58 +0000 Received: by mail-wi0-f172.google.com with SMTP id hi2so10231941wib.5 for ; Thu, 15 May 2014 10:41:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=lVKtpkVmrgpddx5/N88ola6GCQkmIh9YJSGhtfxq+j0=; b=loi0pFkUQHAF71oCvE29k3ssp6rEXJ2aAHM/LVpiGfgOalknkJZg0QTPGHjUyHvXXp lg7GEii97HDYv+SQ7j/dkK5JDXixxgV1tk0f0/TWtNItOozqOE6bhFhH8OQopmBzBEJN 7JKNjbsWfKjBc2h+PR6JMZPO5addbcftKNDOGqTaiHo1AZQrXB7dtShxGSHacbt04NvX zR9mOfEvTmVSUzNMHRAXCMNK4sz27S4D7+lmw3kkIkyUVGIM3ntRw/RXXn8oqB0mD5yr T3JOBF6X8zZTJnCRH4Sq9C0HI19lnmkZ3+mICMi9OpaiMg3CyTb+0obZV7N1LmEVS7TL RHlQ== X-Gm-Message-State: ALoCoQmKVUP6yH5qi5dSKlOarrKcpCDr5k1tLRVzmu5WI4CFh3H5bEHSEkAFc0HrkAT5gN6Yq607 X-Received: by 10.180.93.101 with SMTP id ct5mr9718569wib.23.1400175711516; Thu, 15 May 2014 10:41:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.243.138 with HTTP; Thu, 15 May 2014 10:41:31 -0700 (PDT) In-Reply-To: References: From: Jeff Garzik Date: Thu, 15 May 2014 13:41:31 -0400 Message-ID: To: Andreas Schildbach Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) 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 -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WkzfJ-0000iQ-QU Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] DNS seeds unstable X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2014 17:41:59 -0000 On Thu, May 15, 2014 at 7:50 AM, Andreas Schildbach 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/