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: Sun, 25 May 2014 21:12:10 +0200 [thread overview]
Message-ID: <lltfaa$2lv$1@ger.gmane.org> (raw)
In-Reply-To: <20140523221726.GA30143@petertodd.org>
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?
What particular thing did you fix? It would be good to know for future
outages.
On 05/24/2014 12:17 AM, Peter Todd wrote:
> FWIW
>
> That said, keep in mind the github discussion(1) that was had: if all
> the DNS seeds being down breaks your application, your application is
> broken and insecure. The only exception is initial startup, and even
> then you should have fallbacks such as hardcoded node lists and manual
> peer entry. If for some reason you really do need instant startup, run
> your own centralized high-availability/low-latency nodes; either way
> you're depending on a centralized resource.
>
> 1) https://github.com/bitcoin/bitcoin/pull/4203
next prev parent reply other threads:[~2014-05-25 19: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 [this message]
2014-05-25 20:02 ` Tim
2014-05-26 16:37 ` Peter Todd
2014-05-26 22:12 ` Andreas Schildbach
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='lltfaa$2lv$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