From: Andreas Schildbach <andreas@schildbach•de>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
Date: Tue, 27 May 2014 00:12:05 +0200 [thread overview]
Message-ID: <lm0e7m$thg$1@ger.gmane.org> (raw)
In-Reply-To: <20140526163753.GA18693@petertodd.org>
You're very quick to point at others. Especially since they run software
that had the time to mature for about 30 years, and the protocol didn't
really change since then...
The last time it didn't work, the bug -- non RFC-conformance -- was on
the bitcoin seeders side. ISPs do weird things with DNS, but usually
they stay within the RFC.
Anyway, without logs we don't have a chance to debug this issue. Any
chance you could add simple logging to the seeder?
DNS via HTTP? Never heard of that, at least it sounds weird as well.
On 05/26/2014 06:37 PM, Peter Todd wrote:
> On Sun, May 25, 2014 at 09:12:10PM +0200, Andreas Schildbach wrote:
>> Thanks for looking at the issue.
>>
>> Unfortunately, it still fails for me:
>>
>> $ nslookup testnet-seed.bitcoin.petertodd.org
>> Server: 127.0.1.1
>> Address: 127.0.1.1#53
>>
>> ** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL
>>
>> Like I said, can you look at the logfiles how the requests arrive?
>
> There are no logfiles for DNS requests.
>
> I just checked on EC2 and my cellphone internet connection here in Tel
> Aviv; both work fine. My best guess is that your DNS resolver locally or
> at your ISP is unable to deal with the fact that the second DNS seed
> serving the domain testnet-seed.bitcoin.petertodd.org happens to be down
> right now. Note that some ISP's appear to both run buggy DNS servers,
> and redirect traffic meant to go to Google's 8.8.8 and 8.8.4.4 DNS
> servers to their own servers.
>
> I'd suggest that someone setup an alternate HTTP(S) based DNS seed for
> protocol redundency.
>
>> What particular thing did you fix? It would be good to know for future
>> outages.
>
> Dunno exactly. It appeared to be running fine when I logged into the
> machine, but for whatever reason DNS requests just weren't getting
> resolved. Restarted and it was ok again.
>
>
>
> ------------------------------------------------------------------------------
> The best possible search technologies are now affordable for all companies.
> Download your FREE open source Enterprise Search Engine today!
> Our experts will assist you in its installation for $59/mo, no commitment.
> Test it for FREE on our Cloud platform anytime!
> http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2014-05-26 22:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 22:17 Peter Todd
2014-05-25 19:12 ` Andreas Schildbach
2014-05-25 20:02 ` Tim
2014-05-26 16:37 ` Peter Todd
2014-05-26 22:12 ` Andreas Schildbach [this message]
2014-05-26 22:39 ` Peter Todd
2014-05-26 23:19 ` Andreas Schildbach
2014-05-30 9:43 ` Peter Todd
2014-05-30 13:19 ` Alex Kotenko
2014-05-30 13:41 ` Robert McKay
2014-05-30 14:13 ` Alex Kotenko
2014-05-30 14:51 ` Robert McKay
2014-05-30 15:24 ` Pieter Wuille
2014-05-30 15:40 ` Andreas Schildbach
2014-05-30 15:54 ` Robert McKay
2014-05-30 15:59 ` Pieter Wuille
2014-05-30 16:03 ` Gregory Maxwell
2014-06-01 9:56 ` Alex Kotenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lm0e7m$thg$1@ger.gmane.org' \
--to=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox