Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.100 as permitted sender)
	client-ip=62.13.148.100; envelope-from=pete@petertodd.org;
	helo=outmail148100.authsmtp.co.uk; 
Date: Mon, 26 May 2014 12:37:53 -0400
From: Peter Todd <pete@petertodd.org>
To: Andreas Schildbach <andreas@schildbach.de>
Message-ID: <20140526163753.GA18693@petertodd.org>
References: <20140523221726.GA30143@petertodd.org> <lltfaa$2lv$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s"
Content-Disposition: inline
In-Reply-To: <lltfaa$2lv$1@ger.gmane.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up
 again
Precedence: list


--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, May 25, 2014 at 09:12:10PM +0200, Andreas Schildbach wrote:
> Thanks for looking at the issue.
>=20
> Unfortunately, it still fails for me:
>=20
> $ nslookup testnet-seed.bitcoin.petertodd.org
> Server:		127.0.1.1
> Address:	127.0.1.1#53
>=20
> ** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL
>=20
> 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.

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

--SLDf9lqlvOQaIe6s
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBCAAGBQJTg23hAAoJEBmcgzuo5/CFKGcIAIunCELERdxY6Wc0cNtqzRa9
Py+3p/5BTalXVtW+9zUGOwqyRL4AWtkM2Z6V3w24/VvEczr5MsbrFXoOpd1AKRPa
1kapSx5HDmb2W2eGquTohCB+i3dUmDDfy3DsODY/3ZU2OYkShPCQWSnerJ9Rs1JT
I0+fDl5+NmiiTPPw9XIeNABiMJmJHnJNTUr/Js/rxZ3wD4WFnjXQpRTdnwYUMQmU
SkwU2Fu3WKnLinvoGCsB4Of8nEvcMcJm6RVimDQPU0/CN7tTW7zB8wFGNI3/HVe7
eFo9tlcNdgghwGvF1xlNdRGjqCD3qcQCP2DR0pRCgsVBn0nhu0g/rRz8MI8Jvs4=
=VrRv
-----END PGP SIGNATURE-----

--SLDf9lqlvOQaIe6s--