Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WmXK0-0005BV-6B for bitcoin-development@lists.sourceforge.net; Mon, 19 May 2014 23:50:20 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.169 as permitted sender) client-ip=74.125.82.169; envelope-from=jgarzik@bitpay.com; helo=mail-we0-f169.google.com; Received: from mail-we0-f169.google.com ([74.125.82.169]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WmXJz-0005kA-5O for bitcoin-development@lists.sourceforge.net; Mon, 19 May 2014 23:50:20 +0000 Received: by mail-we0-f169.google.com with SMTP id u56so6353931wes.0 for ; Mon, 19 May 2014 16:50:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=d6OS5qGTDr23D1X/4vwr3N/i5qKVMfyWOdRLg2u9f28=; b=WcrIdFLwnVzMZ8etXiY/NxR8QSO7I4Xtq4Cw6hc6lWqwW+DOYeexyZ2rOUCffvNtkB WKIop+khuLpObJXyXWGsjEaLf65wzi8uqVwzPn6oI2sC1JvNSYO8KSgddiqGNkqpvDi0 9aourzp+q0DeCilCco1JErj/Yvy3Hgx8PqrP5peunJ8uB9JZD5k7laTOXPJwYBiq6mQE fubCoun4L3uxmjjwiNNhf794jIiwX3G/Hyeh+ih19d1C5Dcb3+DVF7QLY3gnjr2tIoVu +a2unMy52FpcblOWIrwI1fgI+7lg46qDUo7Nkvnh49bvZsUcntwwKlMpPASbNkvUCjvX SoNQ== X-Gm-Message-State: ALoCoQlEgkG1EPCsA/WE1PapTAfnOH1wITVw1lfa3+hVtnQOEtTyGJ+6xdL9k1nK/g7g4/Ecy8/S X-Received: by 10.180.14.233 with SMTP id s9mr21237wic.53.1400543412610; Mon, 19 May 2014 16:50:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.240.166 with HTTP; Mon, 19 May 2014 16:49:52 -0700 (PDT) In-Reply-To: <779f3ed92d29cfd6922a92c5d60d3f9d@webmail.mckay.com> References: <09E70F88-DA1C-4E3F-9342-547FB8794EAB@heliacal.net> <779f3ed92d29cfd6922a92c5d60d3f9d@webmail.mckay.com> From: Jeff Garzik Date: Mon, 19 May 2014 19:49:52 -0400 Message-ID: To: Robert McKay Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) 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 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WmXJz-0005kA-5O Cc: Bitcoin Dev 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: Mon, 19 May 2014 23:50:20 -0000 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 -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/