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
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mw@osfda.org>) id 1WmYAF-0001Qr-Lf
for bitcoin-development@lists.sourceforge.net;
Tue, 20 May 2014 00:44:19 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of osfda.org
designates 217.23.13.216 as permitted sender)
client-ip=217.23.13.216; envelope-from=mw@osfda.org;
helo=smtp.osfda.org;
Received: from smtp.osfda.org ([217.23.13.216])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WmYAE-0001Au-F2 for bitcoin-development@lists.sourceforge.net;
Tue, 20 May 2014 00:44:19 +0000
Received: from [192.168.1.117]
(207-38-214-214.c3-0.nyr-ubr1.nyr.ny.cable.rcn.com [207.38.214.214])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by smtp.osfda.org (Postfix) with ESMTPSA id 8ABF513A0434;
Tue, 20 May 2014 02:44:11 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Michael Wozniak <mw@osfda.org>
In-Reply-To: <CAJHLa0O_F3MJc1KJJn+L6AjT-wa8sPunibb4rfWGGUWYSOkVOg@mail.gmail.com>
Date: Mon, 19 May 2014 20:45:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <21D4D9FD-9919-4157-ADFD-C061518E28DA@osfda.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>
To: Jeff Garzik <jgarzik@bitpay.com>
X-Mailer: Apple Mail (2.1874)
X-Spam-Score: -2.3 (--)
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.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-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: 1WmYAE-0001Au-F2
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: Tue, 20 May 2014 00:44:19 -0000
You would set it up as a forwarder, not as a zone transfer to bind. =
That should proxy the request every time and only cache based on any TTL =
that=92s set in the response.
Here=92s an example of how it could work:
=
https://planet.jboss.org/post/setting_up_a_forwarding_dns_server_or_dns_pr=
oxy_with_isc_bind
On May 19, 2014, at 7:49 PM, Jeff Garzik <jgarzik@bitpay.com> 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).
>=20
> 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.
>=20
> That said, if the choice is between no-service and bind, bind it is ;p
>=20
> --=20
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>=20
> =
--------------------------------------------------------------------------=
----
> "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
|
