public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Andreas Schildbach <andreas@schildbach.de>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
Date: Mon, 26 May 2014 12:37:53 -0400	[thread overview]
Message-ID: <20140526163753.GA18693@petertodd.org> (raw)
In-Reply-To: <lltfaa$2lv$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]

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.

-- 
'peter'[:-1]@petertodd.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2014-05-26 16:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 22:17 [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again Peter Todd
2014-05-25 19:12 ` Andreas Schildbach
2014-05-25 20:02   ` Tim
2014-05-26 16:37   ` Peter Todd [this message]
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=20140526163753.GA18693@petertodd.org \
    --to=pete@petertodd.org \
    --cc=andreas@schildbach.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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