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; 
To: Alex Kotenko <alexykot@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Fri, 30 May 2014 14:41:39 +0100
From: Robert McKay <robert@mckay.com>
In-Reply-To: <CALDj+Bax5De1gh1wsz_BjTFTerjzrazZ4SBgEVvYGjhFw3+uEw@mail.gmail.com>
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>
Message-ID: <bce4e62749b3325d884caaf510e9d862@webmail.mckay.com>
User-Agent: Roundcube Webmail/0.5.3
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up
	again
Precedence: list

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. I'm not sure if this can be fixed without hacking the 
bind src, so maybe it wasn't such a great suggestion in the first place. 
Basically I think if bind was returning authorative answers it would 
work, but I can't 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 
> [6]
> and bitcoin-seed.alexykot.me [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 [8] testnet-seed.alexykot.me [9]
>
>  dig @node.alexykot.me [10] bitcoin-seed.alexykot.me [11]
>
> ​But when I try nslookup testnet-seed.alexykot.me [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
>
> 2014-05-30 10:43 GMT+01:00 Peter Todd :
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> On 27 May 2014 02:19:39 GMT+03:00, Andreas Schildbach wrote:
>> >> Hey, really sorry I dont have the time to fix this issue, been
>> >> travelling for a few weeks for my consulting job. If you want to
>> >> step up and volunteer please feel free.
>> >
>> >Im already volunteering. At least I dont get paid for my efforts
>> in
>> >debugging the seed infrastructure.
>>
>> I meant running a seed yourself. Note that Ive only received funds
>> to cover expenses and a trivial amount on top to cover some time -
>> about one and a half hours at my usual rates.
>>
>> Gavin: Speaking of, given it looks like my work will be frequently
>> keeping me out of country and unable to provide any more than a
>> "best effort" attempt at running a seed, Id like to give back the
>> grant funds for doing so. Email me privately with an address to send
>> them too. I have no plans to take it down, however the expectations
>> users have for it arent something I can provide.
>>
>> >Can you verify if your copy of the seeder contains the commit
>> >8dcc006e6256cb746c2b025daf3df41baa26353e ?
>> >
>> >It fixed a bug that has exactly the symptoms we currently see.
>> >
>> >I wonder if the restart of your server actually changed/fixed
>> >anything. If you got a SERVFAIL this may be because you were
>> traveling
>> >through parts of the world that cant reach your server. Did you
>> >actually try at home, before the restart?
>>
>> I checked via the same proxy both times; I believe the endpoint is
>> located in Europe.
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: APG v1.1.1
>>
>> iQFQBAEBCAA6BQJTiFKwMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
>> cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhQFCB/4jypD+xzKVp6fqRUxu
>> v22Rc6PeCbeaPYKmdNu0LbY1G5spB8C8ooaZX6z0Ib/CYobzDPJ+rJNB+c1Fna4N
>> 1IdH7ZsrX0GFaEn7Grnp7D2rtOXGZV+1XGFAateIA/caQ9+rJfqkHLuvOI0Fh+Ua
>> /m857rxUNtA1kObLFS7gfhi2gwXGO6KQ3muS3462hXVVc9j7DhOWQQwJba5PL+Je
>> Eob4WtnF2gVFlCEWevxvflF7j4lW9I/S81yZQDnNW9ATF2mfZVqo26sB0yL6Tm4l
>> KgdKx7+w3khv6QfW9Ilx0Ov3Ml2ZMRhBimpbnENbW4jfklsuRQcM0yx6vXS/lIMz
>> LO5s
>> =Up3N
>> -----END PGP SIGNATURE-----
>>
>>
> 
> ------------------------------------------------------------------------------
>> Time is money. Stop wasting it! Get your web API in 5 minutes.
>> www.restlet.com/download [2]
>> http://p.sf.net/sfu/restlet [3]
>>
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net [4]
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> [5]
>
>
>
> Links:
> ------
> [1] mailto:andreas@schildbach.de
> [2] http://www.restlet.com/download
> [3] http://p.sf.net/sfu/restlet
> [4] mailto:Bitcoin-development@lists.sourceforge.net
> [5] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> [6] http://testnet-seed.alexykot.me
> [7] http://bitcoin-seed.alexykot.me
> [8] http://node.alexykot.me
> [9] http://testnet-seed.alexykot.me
> [10] http://alexykot.me
> [11] http://bitcoin-seed.alexykot.me
> [12] http://testnet-seed.alexykot.me
> [13] mailto:pete@petertodd.org