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
|
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 <mh.in.england@gmail.com>) id 1Qoako-0005k5-Sk
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Aug 2011 12:40:54 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=mh.in.england@gmail.com;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Qoako-00020M-9T
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Aug 2011 12:40:54 +0000
Received: by vws2 with SMTP id 2so666080vws.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 03 Aug 2011 05:40:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.116.67 with SMTP id ju3mr5623754vdb.63.1312375248647; Wed,
03 Aug 2011 05:40:48 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.158.233 with HTTP; Wed, 3 Aug 2011 05:40:48 -0700 (PDT)
In-Reply-To: <4E393EB9.9040005@lavabit.com>
References: <CANEZrP1-BaNmKhSPXSe2sjH0-DPm62_=OQ_S6aCT3-nLdFLLGA@mail.gmail.com>
<1312371499.2322.14.camel@Desktop666>
<4E393EB9.9040005@lavabit.com>
Date: Wed, 3 Aug 2011 14:40:48 +0200
X-Google-Sender-Auth: 4YgxobYPJMUFIOg04_Ptrn7f8IA
Message-ID: <CANEZrP04XcknPRidCndw5VaF1EgzAwyQ4kYxcC3Usnanhxp=Cg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Caleb James DeLisle <calebdelisle@lavabit.com>
Content-Type: multipart/alternative; boundary=bcaec548aa5981f48c04a9992cfe
X-Spam-Score: 0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
1.1 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Qoako-00020M-9T
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] DNS seeds returning gone peers
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: Wed, 03 Aug 2011 12:40:54 -0000
--bcaec548aa5981f48c04a9992cfe
Content-Type: text/plain; charset=UTF-8
>
> Someone I know who runs a moderately large website told me that some ISPs
> cache DNS for as long as a week without regard to TTL.
>
We track DNS disobeyers at Google, as we use it for load balancing (along
with many other large sites).
I'd be kind of surprised if any large/professional ISP disobeyed the TTL
that badly, because it would cause frequent problems reaching popular sites
like anything hosted on Google or Akamai. But randomizing the DNS request
isn't a bad idea.
--bcaec548aa5981f48c04a9992cfe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Someone I know w=
ho runs a moderately large website told me that some ISPs cache DNS for as =
long as a week without regard to TTL.<br>
</blockquote><div><br></div><div>We track DNS disobeyers at Google, as we u=
se it for load balancing (along with many other large sites).</div><div><br=
></div><div>I'd be kind of surprised if any large/professional ISP diso=
beyed the TTL that badly, because it would cause frequent problems reaching=
popular sites like anything hosted on Google or Akamai. But randomizing th=
e DNS request isn't a bad idea.</div>
</div>
--bcaec548aa5981f48c04a9992cfe--
|
