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; 
To: bitcoin-development@lists.sourceforge.net
From: Andreas Schildbach <andreas@schildbach.de>
Date: Thu, 15 May 2014 13:50:29 +0200
Message-ID: <ll29m5$r6c$1@ger.gmane.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
Subject: [Bitcoin-development] DNS seeds unstable
Precedence: list

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.

Current state (seeds taken from bitcoinj):

mainnet:

seed.bitcoin.sipa.be			OK
dnsseed.bluematt.me			OK
dnsseed.bitcoin.dashjr.org		SERVFAIL, tried multiple ISPs
seed.bitcoinstats.com			OK

testnet:

testnet-seed.bitcoin.petertodd.org	SERVFAIL, just from Telefonica
testnet-seed.bluematt.me		OK (but only returns one node)

Note: Telefonica is one of Europe's largest ISPs.

I would try to improve DNS myself, but I'm not capable of writing C. My
"fix" would be to reimplement everything in Java -- I doubt you guys
would be happy with that.