1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
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 <jgarzik@bitpay.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <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>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Mon, 19 May 2014 19:49:52 -0400
Message-ID: <CAJHLa0O_F3MJc1KJJn+L6AjT-wa8sPunibb4rfWGGUWYSOkVOg@mail.gmail.com>
To: Robert McKay <robert@mckay.com>
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 <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds unstable
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 19 May 2014 23:50:20 -0000
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
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
