Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27 May 2014 02:19:39 GMT+03:00, Andreas Schildbach andr...@schildbach.de wrote: Hey, really sorry I don't 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. I'm already volunteering. At least I don't get paid for my efforts in debugging the seed infrastructure. I meant running a seed yourself. Note that I've 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, I'd 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 aren't 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 can't 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 http://p.sf.net/sfu/restlet ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
Hi Peter I've setup DNS seeds myself a week ago, at testnet-seed.alexykot.me and bitcoin-seed.alexykot.me, but there is a problem with DNS settings that we with Andreas couldn't 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 testnet-seed.alexykot.me dig @node.alexykot.me bitcoin-seed.alexykot.me But when I try nslookup testnet-seed.alexykot.me - it fails. I guess the problem is in my DNS settings but I can't 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 p...@petertodd.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27 May 2014 02:19:39 GMT+03:00, Andreas Schildbach andr...@schildbach.de wrote: Hey, really sorry I don't 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. I'm already volunteering. At least I don't get paid for my efforts in debugging the seed infrastructure. I meant running a seed yourself. Note that I've 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, I'd 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 aren't 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 can't 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 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___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
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:andr...@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:p...@petertodd.org -- 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
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
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:rob...@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
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
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 rob...@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:rob...@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 -- Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
On Fri, May 30, 2014 at 5:40 PM, Andreas Schildbach andr...@schildbach.de 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. That's what Matt's implementation is doing. You don't have to run mine :) I chose not to do so, as I wanted to be able to serve a different response to every query, but more diversity is a good thing. -- Pieter -- 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
Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
On Fri, May 30, 2014 at 8:40 AM, Andreas Schildbach andr...@schildbach.de 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. We'd used an approach like that previously and I believe it produced fairly bad load imbalances, especially since some resolvers only pass on a single result. And that was before there was a wide deployment of broken client software that trusted the dnsseeds exclusively. -- 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
