Thanks Alex, you're my hero of the day (-:
Your seed works well for me. Here is a PR for bitcoinj:
https://github.com/bitcoinj/bitcoinj/pull/101
On 06/11/2014 03:57 PM, Alex Kotenko wrote:
> Hi all
>
>
> It took some time, but now my testnet seed is fully operational. In fact
> I've dropped a
Hi all
It took some time, but now my testnet seed is fully operational. In fact
I've dropped an earlier idea of DNS forwarding and now serving only testnet
seed, as it is more important atm than a mainnet one.
Testnet seed is available at testnet-seed.alexykot.me.
Please check and let me know if
Hmmm, not for me:
$ nslookup bitcoin-seed.alexykot.me
Server: 127.0.1.1
Address:127.0.1.1#53
** server can't find bitcoin-seed.alexykot.me: SERVFAIL
$ nslookup testnet-seed.alexykot.me
Server: 127.0.1.1
Address:127.0.1.1#53
** server can't find testnet-seed.alexy
Misunderstanding. Both seeds are available on port 53 via BIND forwarding.
Just also each DNS seed is available separately on it's own port.
Best regards,
Alex Kotenko
2014-05-21 12:03 GMT+01:00 Andreas Schildbach :
> Great, thanks for this contribution!
>
> Do you plan to have your seeds reac
Great, thanks for this contribution!
Do you plan to have your seeds reachable on port 53 eventually?
Currently bitcoinj cannot deal with nonstandard ports I think.
On 05/21/2014 11:23 AM, Alex Kotenko wrote:
> okay, I've set it up with bind forwarding requests to two dnsseeds
> running on separa
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
mai
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
>> wrote:
>>> It should be possible to configure bind as a DNS forwarder.. this
>>> can
>>> be done in a zone context.. then you can for
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’s set
in the response.
Here’s an example of how it could work:
https://planet.jboss.org/post/setting_up_a_forwarding_dns_server_or_dns_proxy_with_isc
On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote:
> On Mon, May 19, 2014 at 4:36 PM, Robert McKay
> 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
On Mon, May 19, 2014 at 4:36 PM, Robert McKay 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 sam
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
I’m not familiar with how the daemon works, however could you set up two
daemons listening local on different ports and with a separate daemon or normal
dns server that proxies incoming queries to either domain? I don’t know if
standard DNS servers would support that, or if you would need a cust
Well, it's possible theoretically, but will need another piece of custom
software that will understand DNS protocol and proxy it correctly based on
actual incoming DNS queries.
On 19 May 2014 21:22, "Michael Wozniak" wrote:
> I’m not familiar with how the daemon works, however could you set up tw
Hmm, I've mostly setup what's promised, testing DNS seeds now. There is one
problem I see that I can't really solve myself.
This dnsseed daemon cannot serve more than one name at once, which means
that I cannot serve testnet and mainnet seeds off one daemon instance which
means I need to buy two IP
On 05/17/2014 02:02 PM, Alex Kotenko wrote:
> So, my understanding is that atm we have no working DNS seeds at the
> testnet3, right? There are two DNS seeds known, of which one is
> unreachable atm, and another one is giving just one IP address, which is
> also a dead node.
Yes, that's my under
Agree.
So, my understanding is that atm we have no working DNS seeds at the
testnet3, right? There are two DNS seeds known, of which one is unreachable
atm, and another one is giving just one IP address, which is also a dead
node.
If I'll start a DNS seed of my own and make sure it works well, wi
I think the best way to contribute to the infrastructure is actually
what we're doing: Test the current infrastructure and point out where it
is not working. Trying to find solutions for problems.
There is nothing gained by throwing additional hardware at a problem if
the problem itself isn't unde
Oops, missed the lost
On May 16, 2014 3:04:40 PM EDT, Matt Corallo wrote:
>Oh, I missed that this was the testnet seed. Yea, that one never got
>set
>up properly and was just pointing to a static seed node (that is now
>down...). The mainnet seed actually works.
>
>On 05/16/14 19:01, Laszlo Hanye
Ok, what do I need to do? How do I host a testnet seed myself?
Best regards,
Alex Kotenko
2014-05-16 23:02 GMT+01:00 Jeff Garzik :
> There are only two testnet seeds listed in bitcoind, and one of them
> returns SERVFAIL (testnet-seed.bitcoin.petertodd.org) and the other
> just returns one A re
There are only two testnet seeds listed in bitcoind, and one of them
returns SERVFAIL (testnet-seed.bitcoin.petertodd.org) and the other
just returns one A record (testnet-seed.bluematt.me). No idea what
seeds bitcoinj uses.
If you are going to depend on testnet, especially for an important
demo.
On Friday, May 16, 2014 5:17:17 PM Rob Golding wrote:
> > > dnsseed.bitcoin.dashjr.orgSERVFAIL, tried multiple ISPs
>
> dnsseed.bitcoin.dashjr.org. 60 IN NS jun.dashjr.org.
> but jun.dashjr.org isn't responding to dns queries (as at 18.10 GMT
> 2014-05-16)
>
> that woul
For example just now:
$ nslookup testnet-seed.bluematt.me
Server: 127.0.1.1
Address:127.0.1.1#53
Non-authoritative answer:
testnet-seed.bluematt.mecanonical name = bitcoin-seednode.bluematt.me.
bitcoin-seednode.bluematt.mecanonical name = desktopv2.bluematt.me.
Name:
This is very strange...when did you run this test and can anyone else
reproduce this?
Matt
On 05/15/14 11:50, Andreas Schildbach wrote:
> testnet-seed.bluematt.me OK (but only returns one node)
--
"Accelerat
Luke's server has been having issues with ipv4 routing lately anyway, even
ignoring any DNS issues.
Nick
On May 16, 2014 12:17:17 PM CDT, Rob Golding wrote:
>> > dnsseed.bitcoin.dashjr.org SERVFAIL, tried multiple ISPs
>
>dnsseed.bitcoin.dashjr.org. 60 IN NS jun.dashjr.org.
>
> > dnsseed.bitcoin.dashjr.org SERVFAIL, tried multiple ISPs
dnsseed.bitcoin.dashjr.org. 60 IN NS jun.dashjr.org.
but jun.dashjr.org isn't responding to dns queries (as at 18.10 GMT
2014-05-16)
that would be a fundamental problem with the dns infrastructure for that
domain (an
Hi guys
Just wanted to let you know that Andreas' testnet Bitcoin Wallet doesn't
work because of fail in the peer discovery, and this caused us problems as
we cannot properly demonstrate my XBTerminal POS on the Bitcoin Conference.
Right now I'm booting up an own full node that I will set as tru
It looks like it might be firewalled, probably just need to fix the ACL in EC2.
-Laszlo
On May 16, 2014, at 4:34 PM, Andreas Schildbach wrote:
> Apparently British Telecom also cannot speak to Peter Todd's server.
>
> That another very large ISP in Europe.
>
>
> On 05/15/2014 01:50 PM, Andre
Is Peter Todd's server actually up? The Google public DNS resolver at 8.8.8.8
can't resolve testnet-seed.bitcoin.petertodd.org either (SERVFAIL).
On Friday, 16 May 2014, at 6:34 pm, Andreas Schildbach wrote:
> Apparently British Telecom also cannot speak to Peter Todd's server.
>
> That another
Apparently British Telecom also cannot speak to Peter Todd's server.
That another very large ISP in Europe.
On 05/15/2014 01:50 PM, Andreas Schildbach wrote:
> I'm bringing this issue up again. The current Bitcoin DNS seed
> infrastructure is unstable. I assume this is because of we're using a
>
My android wallet is working OK. Yes it isn't great when seeds have
temporary availability problems but things are still working.
There's a couple of pull reqs outstanding to include hard coded seed peers
and getaddr sourced IPs. Once those are finished and merged in there'll be
more backup paths.
On 05/15/2014 07:48 PM, Gregory Maxwell wrote:
> On Thu, May 15, 2014 at 4:50 AM, Andreas Schildbach
> wrote:
>> I'm bringing this issue up again. The current Bitcoin DNS seed
>> infrastructure is unstable. I assume this is because of we're using a
>> custom DNS implementation which is not 100% co
On Thursday, May 15, 2014 11:50:29 AM Andreas Schildbach wrote:
> dnsseed.bitcoin.dashjr.orgSERVFAIL, tried multiple ISPs
FWIW, this may be a routing issue: I notice various ISPs have been unable to
route to my server over IPv4 today. IPv6 seems to be fine.
Not sure how important DNS
On Thu, May 15, 2014 at 4:50 AM, Andreas Schildbach
wrote:
> I'm bringing this issue up again. The current Bitcoin DNS seed
> infrastructure is unstable. I assume this is because of we're using a
> custom DNS implementation which is not 100% compatible. There have been
> bugs in the past, like a c
On Thu, May 15, 2014 at 7:50 AM, Andreas Schildbach
wrote:
> I'm bringing this issue up again. The current Bitcoin DNS seed
> infrastructure is unstable. I assume this is because of we're using a
> custom DNS implementation which is not 100% compatible. There have been
> bugs in the past, like a c
I am sure the failure here is probably more mundane like a a service not
restarted, or not on auto restart when server is rebooted and such like.
The dns seeder works pretty efficiently in my experience. Maybe we need
more seeders and to include the ability for zone transfers so existing
seeders ca
35 matches
Mail list logo
