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; 
To: bitcoin-development@lists.sourceforge.net
From: Andreas Schildbach <andreas@schildbach.de>
Date: Wed, 21 May 2014 13:03:29 +0200
Message-ID: <lli161$81k$1@ger.gmane.org>
References: <ll29m5$r6c$1@ger.gmane.org>
	<ll5ems$6pt$1@ger.gmane.org>	<09E70F88-DA1C-4E3F-9342-547FB8794EAB@heliacal.net>	<CALDj+BZrn6TBjdVjGkc293SLAAcqzni+-7daFpZAq5gSaL1cKw@mail.gmail.com>	<CAJHLa0OaAKTLR2hL6kReBFcD6FoXYV9AoqMbn0WwqYgtTNtQKw@mail.gmail.com>	<CALDj+BY2jEL6-NwGdrh3wdcmjW_7tEDDxmyiP6woOxCg8bMQKw@mail.gmail.com>	<ll7hps$8gs$1@ger.gmane.org>	<CALDj+BYqMDxv+YYcrEzaZH+qFqUsme3UYuYh5Es7C6FbMZCtpg@mail.gmail.com>	<ll7l9t$m82$1@ger.gmane.org>	<CALDj+BamyawuTgDhzM0AyB5LWNPb_xY_BQeDHqs9t9WLPibiCQ@mail.gmail.com>	<779f3ed92d29cfd6922a92c5d60d3f9d@webmail.mckay.com>	<CAJHLa0O_F3MJc1KJJn+L6AjT-wa8sPunibb4rfWGGUWYSOkVOg@mail.gmail.com>	<0f40d061612966ff809fff04d3f698eb@webmail.mckay.com>	<a9d48b2474c87e6d9b80b567b782ecfa@webmail.mckay.com>
	<CALDj+BZ8U29qKywO=Ejxx-WtKGvEyUg5RoYZb=j07oAOSq57yA@mail.gmail.com>
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
In-Reply-To: <CALDj+BZ8U29qKywO=Ejxx-WtKGvEyUg5RoYZb=j07oAOSq57yA@mail.gmail.com>
Subject: Re: [Bitcoin-development] DNS seeds unstable
Precedence: list

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 <http://node.alexykot.me> bitcoin-seed.alexykot.me
> <http://bitcoin-seed.alexykot.me> A
> or directly
> dig -p 8353 @node.alexykot.me <http://node.alexykot.me>
> bitcoin-seed.alexykot.me <http://bitcoin-seed.alexykot.me> A
> 
> testnet seed
> dig @node.alexykot.me <http://node.alexykot.me> testnet-seed.alexykot.me
> <http://testnet-seed.alexykot.me> A
> or directly
> dig -p 18353 @node.alexykot.me <http://node.alexykot.me>
> testnet-seed.alexykot.me <http://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 <robert@mckay.com
> <mailto:robert@mckay.com>>:
> 
>     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 <robert@mckay.com
>     <mailto:robert@mckay.com>>
>     >> 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
>     <mailto: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
>