summaryrefslogtreecommitdiff
path: root/65/960ad5fdf74e2e20b5daef4b5ffc1c266dbc0f
blob: baa8796f466cfa24514b14c828718afbaf83482e (plain)
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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <robert@mckay.com>) id 1WqP8m-0004ok-CZ
	for bitcoin-development@lists.sourceforge.net;
	Fri, 30 May 2014 15:54:44 +0000
Received-SPF: pass (sog-mx-1.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; 
Received: from mail.mckay.com ([37.1.88.131])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1WqP8k-0004eT-PH
	for bitcoin-development@lists.sourceforge.net;
	Fri, 30 May 2014 15:54:44 +0000
Received: from www-data by mail.mckay.com with local (Exim 4.76)
	(envelope-from <robert@mckay.com>)
	id 1WqP8g-0008C5-C8; Fri, 30 May 2014 16:54:38 +0100
To: Andreas Schildbach <andreas@schildbach.de>
X-PHP-Originating-Script: 0:func.inc
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 30 May 2014 16:54:38 +0100
From: Robert McKay <robert@mckay.com>
In-Reply-To: <lma8om$4va$1@ger.gmane.org>
References: <20140523221726.GA30143@petertodd.org>
	"<lltfaa$2lv$1@ger.gmane.org>" <20140526163753.GA18693@petertodd.org>
	"<lm0e7m$thg$1@ger.gmane.org>	<b6884e2a-42b7-4c3f-a034-3a466aeec751@email.android.com>	<lm0i6b$4m9$1@ger.gmane.org>	<cae15a82-73f7-4703-bc7d-f433b002e06e@email.android.com>	<CALDj+Bax5De1gh1wsz_BjTFTerjzrazZ4SBgEVvYGjhFw3+uEw@mail.gmail.com>	<bce4e62749b3325d884caaf510e9d862@webmail.mckay.com>	<CALDj+BZSYojZ1kQqb_5zrpjc=5E94bbZ7a0PG4bkZx38J0zHWQ@mail.gmail.com>"
	<48331d04b68b3d6554b4e59e97ffbafe@webmail.mckay.com>
	<CAPg+sBj83Dnrk5nuBenATgJGD3ZJKC-BzcKe+03fJGF93qs+Rw@mail.gmail.com>
	<lma8om$4va$1@ger.gmane.org>
Message-ID: <759940f6ac0a5ab33d9bc233edf69f33@webmail.mckay.com>
X-Sender: robert@mckay.com
User-Agent: Roundcube Webmail/0.5.3
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: 1WqP8k-0004eT-PH
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up
	again
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: Fri, 30 May 2014 15:54:44 -0000

A simple hack would be to crontab up a couple of dig scripts that every 
minute 'dig' (dig's output is in bind zonefile format) the bitcoin-seed 
and write the results to two zonefiles that bind can then serve.

Basically

dig @127.0.0.1 -p 5353 > zonefile1.zone
dig @127.0.0.1 -p 5354 > zonefile2.zone

pkill -HUP named

Ugly, but should work.

Rob

On Fri, 30 May 2014 17:40:06 +0200, Andreas Schildbach wrote:
> I maybe have made this suggestion in the past, but why don't we teach
> the seeder (or maybe even plain bitcoind) how to write a zone file 
> and
> then use matured DNS servers to serve this zone?
>
> I admit I never ran my own DNS so I'm not sure if that can work -- 
> but
> to me it sounds like the easiest approach plus everyone can just use
> stock server software.
>
>
> On 05/30/2014 05:24 PM, Pieter Wuille wrote:
>> I don't think it would be too hard to add support for a option to 
>> the
>> seeder "for non-matching requests, forward to other DNS server at
>> IP:PORT", so you could cascade them.
>>
>> On Fri, May 30, 2014 at 4:51 PM, Robert McKay <robert@mckay.com> 
>> wrote:
>>> No, I don't think so. The problem is the 'aa' flag is missing (see 
>>> the
>>> 'flags' section in dig). Perhaps if you could suppress the 
>>> authority
>>> records the recursor would give up and just accept the 
>>> non-authorative
>>> answer, but that isn't a good solution even if it might work for 
>>> some
>>> resolvers.
>>>
>>> Rob
>>>
>>> On Fri, 30 May 2014 15:13:36 +0100, Alex Kotenko wrote:
>>>> Hmm, you might be right, as queries
>>>> dig @node.alexykot.me [8] testnet-seed.alexykot.me [9]
>>>>
>>>> and
>>>>  dig @node.alexykot.me [10] -p 18353 testnet-seed.alexykot.me
>>>> [11]
>>>>
>>>> are giving different authority sections.
>>>>
>>>> Hmm, but if I setup custom SOA record for it - it should work,
>>>> right?
>>>>  What SOA name should it be actually, assuming that NS record for
>>>> testnet-seed.alexykot.me [12] is pointing at alexykot.me [13]?
>>>>
>>>> Best regards,
>>>>
>>>> Alex Kotenko
>>>>
>>>> 2014-05-30 14:41 GMT+01:00 Robert McKay :
>>>>
>>>>> Hi Alex,
>>>>>
>>>>> I think the problem is with my suggestion to use bind 
>>>>> forwarding..
>>>>> basically bind is stripping off the authorative answer bit in the
>>>>> reply.. this causes the recursor to go into a loop chasing the
>>>>> authority server which again returns a non-authoritve answer with
>>>>> itself as the authority again. Im not sure if this can be fixed
>>>>> without hacking the bind src, so maybe it wasnt such a great
>>>>> suggestion in the first place. Basically I think if bind was
>>>>> returning authorative answers it would work, but I cant see any 
>>>>> way
>>>>> to make that happen in the bind configuration.
>>>>>
>>>>> Rob
>>>>>
>>>>> On Fri, 30 May 2014 14:19:05 +0100, Alex Kotenko wrote:
>>>>>
>>>>>> Hi Peter
>>>>>>
>>>>>> Ive setup DNS seeds myself a week ago, at
>>>>>> testnet-seed.alexykot.me [1] [6]
>>>>>> and bitcoin-seed.alexykot.me [2] [7], but there is a problem 
>>>>>> with
>>>>>> DNS
>>>>>> settings that we with Andreas couldnt sort out quickly.
>>>>>>
>>>>>> The problem itself is that I can reach my nameserver and get
>>>>>> dnsseed
>>>>>> response if I query it directly with
>>>>>>  dig @node.alexykot.me [3] [8] testnet-seed.alexykot.me [4] [9]
>>>>>>
>>>>>>  dig @node.alexykot.me [5] [10] bitcoin-seed.alexykot.me [6]
>>>>>> [11]
>>>>>>
>>>>>> But when I try nslookup testnet-seed.alexykot.me [7] [12] -
>>>>>> it
>>>>>> fails.
>>>>>> I guess the problem is in my DNS settings but I cant figure out
>>>>>> what
>>>>>> is it.
>>>>>>
>>>>>> S o could you share
>>>>>> how you configured DNS
>>>>>>   for your seed
>>>>>> to help me debug
>>>>>>  mine
>>>>>> ?
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Alex Kotenko
>>>>>>
>>>>>>
>>>>
>>>>
>>>> Links:
>>>> ------
>>>> [1] http://testnet-seed.alexykot.me
>>>> [2] http://bitcoin-seed.alexykot.me
>>>> [3] http://node.alexykot.me
>>>> [4] http://testnet-seed.alexykot.me
>>>> [5] http://node.alexykot.me
>>>> [6] http://bitcoin-seed.alexykot.me
>>>> [7] http://testnet-seed.alexykot.me
>>>> [8] http://node.alexykot.me/
>>>> [9] http://testnet-seed.alexykot.me/
>>>> [10] http://node.alexykot.me/
>>>> [11] http://testnet-seed.alexykot.me/
>>>> [12] http://testnet-seed.alexykot.me
>>>> [13] http://alexykot.me
>>>> [14] mailto:robert@mckay.com
>>>
>>>
>>> 
>>> ------------------------------------------------------------------------------
>>> Time is money. Stop wasting it! Get your web API in 5 minutes.
>>> www.restlet.com/download
>>> http://p.sf.net/sfu/restlet
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>> 
>> ------------------------------------------------------------------------------
>> Time is money. Stop wasting it! Get your web API in 5 minutes.
>> www.restlet.com/download
>> http://p.sf.net/sfu/restlet
>>
>
>
>
> 
> ------------------------------------------------------------------------------
> Time is money. Stop wasting it! Get your web API in 5 minutes.
> www.restlet.com/download
> http://p.sf.net/sfu/restlet
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development