Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of mckay.com
	designates 37.1.88.131 as permitted sender)
	client-ip=37.1.88.131; envelope-from=robert@mckay.com;
	helo=mail.mckay.com; 
To: Jeff Garzik <jgarzik@bitpay.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 20 May 2014 01:44:29 +0100
From: Robert McKay <robert@mckay.com>
In-Reply-To: <CAJHLa0O_F3MJc1KJJn+L6AjT-wa8sPunibb4rfWGGUWYSOkVOg@mail.gmail.com>
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>
Message-ID: <0f40d061612966ff809fff04d3f698eb@webmail.mckay.com>
User-Agent: Roundcube Webmail/0.5.3
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds unstable
Precedence: list

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> 
> 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.

Rob