Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wldu0-0006VR-5Z for bitcoin-development@lists.sourceforge.net; Sat, 17 May 2014 12:39:48 +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 1Wldtw-0002d6-U1 for bitcoin-development@lists.sourceforge.net; Sat, 17 May 2014 12:39:48 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Wldtp-0001vI-7G for bitcoin-development@lists.sourceforge.net; Sat, 17 May 2014 14:39:37 +0200 Received: from e179039129.adsl.alicedsl.de ([85.179.39.129]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 17 May 2014 14:39:37 +0200 Received: from andreas by e179039129.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 17 May 2014 14:39:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Sat, 17 May 2014 14:39:25 +0200 Message-ID: References: <09E70F88-DA1C-4E3F-9342-547FB8794EAB@heliacal.net> 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: e179039129.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. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -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] -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: 1Wldtw-0002d6-U1 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: Sat, 17 May 2014 12:39:48 -0000 On 05/17/2014 02:02 PM, Alex Kotenko wrote: > So, my understanding is that atm we have no working DNS seeds at the > testnet3, right? There are two DNS seeds known, of which one is > unreachable atm, and another one is giving just one IP address, which is > also a dead node. Yes, that's my understanding too. > If I'll start a DNS seed of my own and make sure it works well, will > this help? Yes, definately. > I've found this DNS seeder daemon > , and it seems to be exactly > what I need to run a DNS seeder myself. Afaik this is what most of the other seeds are using, yes. > So if my understanding is correct, I'll setup a DNS seeds for mainnet > and for testnet at bitcoin-seed.alexykot.me > and testnet-seed.alexykot.me > , and also a well connected nodes for > mainnet and testnet on the same server. > Is this a good plan? Will this all help? Sound great! Let me know if you've got something to test.