Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wn4JM-0007Gp-0W for bitcoin-development@lists.sourceforge.net; Wed, 21 May 2014 11:03:52 +0000 Received-SPF: pass (sog-mx-1.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-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Wn4JJ-0003Ck-TH for bitcoin-development@lists.sourceforge.net; Wed, 21 May 2014 11:03:51 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Wn4JA-00062r-Bk for bitcoin-development@lists.sourceforge.net; Wed, 21 May 2014 13:03:40 +0200 Received: from e177084150.adsl.alicedsl.de ([85.177.84.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 May 2014 13:03:40 +0200 Received: from andreas by e177084150.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 May 2014 13:03:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Wed, 21 May 2014 13:03:29 +0200 Message-ID: References: <09E70F88-DA1C-4E3F-9342-547FB8794EAB@heliacal.net> <779f3ed92d29cfd6922a92c5d60d3f9d@webmail.mckay.com> <0f40d061612966ff809fff04d3f698eb@webmail.mckay.com> 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: e177084150.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: 1Wn4JJ-0003Ck-TH 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: Wed, 21 May 2014 11:03:52 -0000 Great, thanks for this contribution! Do you plan to have your seeds reachable on port 53 eventually? Currently bitcoinj cannot deal with nonstandard ports I think. On 05/21/2014 11:23 AM, Alex Kotenko wrote: > okay, I've set it up with bind forwarding requests to two dnsseeds > running on separate ports. Though I see a problem with testnet DNS seed > itself. It runs, but somehow it only returns one IP address. Exactly > same DNS seeder looking for mainnet nodes is working fine. > > You can reach seeds through > mainnet seed: > dig @node.alexykot.me bitcoin-seed.alexykot.me > A > or directly > dig -p 8353 @node.alexykot.me > bitcoin-seed.alexykot.me A > > testnet seed > dig @node.alexykot.me testnet-seed.alexykot.me > A > or directly > dig -p 18353 @node.alexykot.me > testnet-seed.alexykot.me A > > So what can be the problem with testnet DNS seeder? > > > Best regards, > Alex Kotenko > > > 2014-05-20 1:50 GMT+01:00 Robert McKay >: > > On Tue, 20 May 2014 01:44:29 +0100, Robert McKay wrote: > > On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote: > >> On Mon, May 19, 2014 at 4:36 PM, Robert McKay > > >> wrote: > >>> It should be possible to configure bind as a DNS forwarder.. this > >>> can > >>> be done in a zone context.. then you can forward the different > >>> zones > >>> to > >>> different dnsseed daemons running on different non-public IPs or > >>> two > >>> different ports on the same IP (or on one single non-public IP > >>> since > >>> there's really no reason to expose the dnsseed directly daemon at > >>> all). > >> > >> Quite the opposite. dnsseed data rotates through a lot of addresses > >> if available. Using the bind/zone-xfer system would result in fewer > >> total addresses going through to the clients, thanks to the addition > >> of caching levels that the bind/zone-xfer system brings. > >> > >> That said, if the choice is between no-service and bind, bind it is > >> ;p > > > > Setting it up as a zone forwarder causes each request to go through > > to > > the dnsseed backend for each request. > > This stackoverflow describes a similar situation; > > http://stackoverflow.com/questions/15338232/how-to-forward-a-subzone > > you can additionally specify the port to forward too; > > http://www.zytrax.com/books/dns/ch7/queries.html#forwarders > > it should be possible to forward to different ports on 127.0.0.1 for > each dnsseed instance. > > Rob > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >