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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1WlPxC-0001Xk-Mi
for bitcoin-development@lists.sourceforge.net;
Fri, 16 May 2014 21:46:10 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([192.3.11.21])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WlPxA-0002Mb-5y for bitcoin-development@lists.sourceforge.net;
Fri, 16 May 2014 21:46:10 +0000
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:be5f:f4ff:febf:4f76])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id F2B0E10837D2;
Fri, 16 May 2014 21:46:40 +0000 (UTC)
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 16 May 2014 21:46:00 +0000
User-Agent: KMail/1.13.7 (Linux/3.14.2-gentoo; KDE/4.12.5; x86_64; ; )
References: <ll29m5$r6c$1@ger.gmane.org> <ll5ems$6pt$1@ger.gmane.org>
<009d01cf712a$b0577340$110659c0$@golding@astutium.com>
In-Reply-To: <009d01cf712a$b0577340$110659c0$@golding@astutium.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201405162146.01429.luke@dashjr.org>
X-Spam-Score: -0.7 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1WlPxA-0002Mb-5y
Subject: Re: [Bitcoin-development] DNS seeds unstable
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: Fri, 16 May 2014 21:46:10 -0000
On Friday, May 16, 2014 5:17:17 PM Rob Golding wrote:
> > > dnsseed.bitcoin.dashjr.org SERVFAIL, tried multiple ISPs
>
> dnsseed.bitcoin.dashjr.org. 60 IN NS jun.dashjr.org.
> but jun.dashjr.org isn't responding to dns queries (as at 18.10 GMT
> 2014-05-16)
>
> that would be a fundamental problem with the dns infrastructure for that
> domain (and the sub-hosts/records) , with the authoritive server not
> replying to the dns query
jun.dashjr.org has resolved 130 requests in the past ~12 hours, and I can see
it resolving more in tcpdump. I do observe two potential problems, however:
- For the past 24-48 hours, there seem to be some significant routing problems
on the IPv4 internet, resulting in people using various diverse ISPs
(including myself at home) being unable to route to any of my servers. This
issue doesn't affect IPv6, however.
- The DNS seeder seems to only be responding to requests received over IPv4.
This means IPv6 DNS servers get no response. :(
Luke
|
