1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1WoxuX-0001NZ-Dh
for bitcoin-development@lists.sourceforge.net;
Mon, 26 May 2014 16:38:05 +0000
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;
Received: from outmail148100.authsmtp.co.uk ([62.13.148.100])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WoxuV-0007fc-UI for bitcoin-development@lists.sourceforge.net;
Mon, 26 May 2014 16:38:05 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s4QGbvwY073224;
Mon, 26 May 2014 17:37:57 +0100 (BST)
Received: from petertodd.org (petertodd.org [174.129.28.249])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s4QGbr5B041814
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Mon, 26 May 2014 17:37:55 +0100 (BST)
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)
X-Server-Quench: 172385c5-e4f4-11e3-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAQUFVQNAgsB AmIbWlNeU1p7XGU7 ag1VcwRfa1RMVxto
VEFWR1pVCwQmQhhg cUxcV2tycwROeXo+ bUZgVj5aW0Z5fUMu
R1MBETsCeGZhPWMC AkNRcR5UcAFPdx8U a1UrBXRDAzANdhES
HhM4ODE3eDlSNilR RRkIIFQOdA4XEyUg QR0eWC4iEEFDTSQv
JBsnLBgEEVocKFk1 PVdnXkgXex4JQhBG fQlEDyZYITEA
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 174.129.28.249/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1WoxuV-0007fc-UI
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up
again
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 26 May 2014 16:38:05 -0000
--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--
|
