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
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <alexy.kot.all@gmail.com>) id 1Wn2ke-0000SB-8R
for bitcoin-development@lists.sourceforge.net;
Wed, 21 May 2014 09:23:56 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.181 as permitted sender)
client-ip=209.85.220.181; envelope-from=alexy.kot.all@gmail.com;
helo=mail-vc0-f181.google.com;
Received: from mail-vc0-f181.google.com ([209.85.220.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wn2kc-0001tb-5E
for bitcoin-development@lists.sourceforge.net;
Wed, 21 May 2014 09:23:56 +0000
Received: by mail-vc0-f181.google.com with SMTP id ld13so2122458vcb.40
for <bitcoin-development@lists.sourceforge.net>;
Wed, 21 May 2014 02:23:48 -0700 (PDT)
X-Received: by 10.58.195.202 with SMTP id ig10mr7107846vec.33.1400664228593;
Wed, 21 May 2014 02:23:48 -0700 (PDT)
MIME-Version: 1.0
Sender: alexy.kot.all@gmail.com
Received: by 10.58.211.135 with HTTP; Wed, 21 May 2014 02:23:08 -0700 (PDT)
In-Reply-To: <a9d48b2474c87e6d9b80b567b782ecfa@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>
<CAJHLa0O_F3MJc1KJJn+L6AjT-wa8sPunibb4rfWGGUWYSOkVOg@mail.gmail.com>
<0f40d061612966ff809fff04d3f698eb@webmail.mckay.com>
<a9d48b2474c87e6d9b80b567b782ecfa@webmail.mckay.com>
From: Alex Kotenko <alexykot@gmail.com>
Date: Wed, 21 May 2014 10:23:08 +0100
X-Google-Sender-Auth: O1biOgyiSjvE7fzt8c8gKxW4_5Q
Message-ID: <CALDj+BZ8U29qKywO=Ejxx-WtKGvEyUg5RoYZb=j07oAOSq57yA@mail.gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b66fce7cb880104f9e58d74
X-Spam-Score: 0.9 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(alexy.kot.all[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
1.0 HTML_MESSAGE BODY: HTML included in message
0.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word
-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: 1Wn2kc-0001tb-5E
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: Wed, 21 May 2014 09:23:56 -0000
--047d7b66fce7cb880104f9e58d74
Content-Type: text/plain; charset=UTF-8
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 bitcoin-seed.alexykot.me A
or directly
dig -p 8353 @node.alexykot.me bitcoin-seed.alexykot.me A
testnet seed
dig @node.alexykot.me testnet-seed.alexykot.me A
or directly
dig -p 18353 @node.alexykot.me 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>:
> 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>
> >> 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
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b66fce7cb880104f9e58d74
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:'cou=
rier new',monospace;color:rgb(0,51,0)">okay, I've set it up with bi=
nd 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 re=
turns one IP address. Exactly same DNS seeder looking for mainnet nodes is =
working fine.=C2=A0</div>
<div class=3D"gmail_default" style=3D"font-family:'courier new',mon=
ospace;color:rgb(0,51,0)"><br></div><div class=3D"gmail_default" style=3D"f=
ont-family:'courier new',monospace;color:rgb(0,51,0)">You can reach=
seeds through</div>
<div class=3D"gmail_default" style=3D"font-family:'courier new',mon=
ospace;color:rgb(0,51,0)">mainnet seed:</div><div class=3D"gmail_default" s=
tyle><font color=3D"#003300" face=3D"courier new, monospace">dig @<a href=
=3D"http://node.alexykot.me">node.alexykot.me</a> <a href=3D"http://bitcoin=
-seed.alexykot.me">bitcoin-seed.alexykot.me</a> A</font><br>
</div><div class=3D"gmail_default" style><font color=3D"#003300" face=3D"co=
urier new, monospace">or directly</font></div><div class=3D"gmail_default" =
style><font color=3D"#003300" face=3D"courier new, monospace">dig -p 8353 @=
<a href=3D"http://node.alexykot.me">node.alexykot.me</a> <a href=3D"http://=
bitcoin-seed.alexykot.me">bitcoin-seed.alexykot.me</a> A<br>
</font></div><div class=3D"gmail_default" style><font color=3D"#003300" fac=
e=3D"courier new, monospace"><br></font></div><div class=3D"gmail_default" =
style><font color=3D"#003300" face=3D"courier new, monospace">testnet seed<=
/font></div>
<div class=3D"gmail_default" style><font color=3D"#003300" face=3D"courier =
new, monospace">dig @<a href=3D"http://node.alexykot.me">node.alexykot.me</=
a> <a href=3D"http://testnet-seed.alexykot.me">testnet-seed.alexykot.me</a>=
A</font><br>
</div><div class=3D"gmail_default" style><div class=3D"gmail_default"><font=
color=3D"#003300" face=3D"courier new, monospace">or directly</font></div>=
<div><div class=3D"gmail_default"><font color=3D"#003300" face=3D"courier n=
ew, monospace">dig -p 18353 @<a href=3D"http://node.alexykot.me">node.alexy=
kot.me</a> <a href=3D"http://testnet-seed.alexykot.me">testnet-seed.alexyko=
t.me</a> A</font><br>
</div><div class=3D"gmail_default"></div></div></div><div class=3D"gmail_de=
fault" style=3D"font-family:'courier new',monospace;color:rgb(0,51,=
0)"><br></div><div class=3D"gmail_default" style=3D"font-family:'courie=
r new',monospace;color:rgb(0,51,0)">
So what can be the problem with testnet DNS seeder?</div><div class=3D"gmai=
l_default" style=3D"font-family:'courier new',monospace;color:rgb(0=
,51,0)"><br></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div di=
r=3D"ltr">
<span style=3D"color:rgb(0,51,0);font-family:'courier new',monospac=
e">Best regards,=C2=A0</span><div><div><div style=3D"text-align:left"><font=
color=3D"#003300" face=3D"'courier new', monospace" style=3D"text-=
align:-webkit-auto">Alex Kotenko</font></div>
</div></div></div></div>
<br><br><div class=3D"gmail_quote">2014-05-20 1:50 GMT+01:00 Robert McKay <=
span dir=3D"ltr"><<a href=3D"mailto:robert@mckay.com" target=3D"_blank">=
robert@mckay.com</a>></span>:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
<div class=3D""><div class=3D"h5">On Tue, 20 May 2014 01:44:29 +0100, Rober=
t McKay wrote:<br>
> On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote:<br>
>> On Mon, May 19, 2014 at 4:36 PM, Robert McKay <<a href=3D"mailt=
o:robert@mckay.com">robert@mckay.com</a>><br>
>> wrote:<br>
>>> It should be possible to configure bind as a DNS forwarder.. t=
his<br>
>>> can<br>
>>> be done in a zone context.. then you can forward the different=
<br>
>>> zones<br>
>>> to<br>
>>> different dnsseed daemons running on different non-public IPs =
or<br>
>>> two<br>
>>> different ports on the same IP (or on one single non-public IP=
<br>
>>> since<br>
>>> there's really no reason to expose the dnsseed directly da=
emon at<br>
>>> all).<br>
>><br>
>> Quite the opposite. =C2=A0dnsseed data rotates through a lot of ad=
dresses<br>
>> if available. =C2=A0Using the bind/zone-xfer system would result i=
n fewer<br>
>> total addresses going through to the clients, thanks to the additi=
on<br>
>> of caching levels that the bind/zone-xfer system brings.<br>
>><br>
>> That said, if the choice is between no-service and bind, bind it i=
s<br>
>> ;p<br>
><br>
> Setting it up as a zone forwarder causes each request to go through<br=
>
> to<br>
> the dnsseed backend for each request.<br>
<br>
</div></div>This stackoverflow describes a similar situation;<br>
<br>
<a href=3D"http://stackoverflow.com/questions/15338232/how-to-forward-a-sub=
zone" target=3D"_blank">http://stackoverflow.com/questions/15338232/how-to-=
forward-a-subzone</a><br>
<br>
you can additionally specify the port to forward too;<br>
<br>
<a href=3D"http://www.zytrax.com/books/dns/ch7/queries.html#forwarders" tar=
get=3D"_blank">http://www.zytrax.com/books/dns/ch7/queries.html#forwarders<=
/a><br>
<br>
it should be possible to forward to different ports on 127.0.0.1 for<br>
each dnsseed instance.<br>
<br>
Rob<br>
<div class=3D""><br>
---------------------------------------------------------------------------=
---<br>
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE=
<br>
Instantly run your Selenium tests across 300+ browser/OS combos.<br>
Get unparalleled scalability from the best Selenium testing platform availa=
ble<br>
Simple to use. Nothing to install. Get started now for free."<br>
<a href=3D"http://p.sf.net/sfu/SauceLabs" target=3D"_blank">http://p.sf.net=
/sfu/SauceLabs</a><br>
</div><div class=3D"">_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
</div><a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-devel=
opment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitc=
oin-development</a><br>
</blockquote></div><br></div></div>
--047d7b66fce7cb880104f9e58d74--
|