From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WlEFD-0008Qn-G8 for bitcoin-development@lists.sourceforge.net; Fri, 16 May 2014 09:15:59 +0000 Received-SPF: pass (sog-mx-2.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-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WlEFC-0007vO-J5 for bitcoin-development@lists.sourceforge.net; Fri, 16 May 2014 09:15:59 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WlEF4-0004R9-CE for bitcoin-development@lists.sourceforge.net; Fri, 16 May 2014 11:15:50 +0200 Received: from e179076090.adsl.alicedsl.de ([85.179.76.90]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 May 2014 11:15:50 +0200 Received: from andreas by e179076090.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 May 2014 11:15:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Fri, 16 May 2014 11:15:34 +0200 Message-ID: References: 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: e179076090.adsl.alicedsl.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 In-Reply-To: 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: 1WlEFC-0007vO-J5 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: Fri, 16 May 2014 09:15:59 -0000 On 05/15/2014 07:48 PM, Gregory Maxwell wrote: > On Thu, May 15, 2014 at 4: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. > > If software is using the DNS seeds in a way where one or two being > unavailable is problematic, then the software may be using them > poorly. > > Generally DNS seeds should only be used as fast connectivity hints, > primarily for initial connectivity. Relying on them exclusively > increases isolation vulnerabilities (e.g. because the dns seed > operators or any ISP or network attacker on the path between you and > the seeds can replace the results with ones that isolate you on a > bogus network). I just used "nslookup", after seeing the issues in bitcoinj. I agree that clients should be robust regarding DNS lookups (and bitcoinj isn't), but still I think the first step needs to be maintaining a quality infrastructure.