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 ) 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 ; 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: <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: From: Mike Hearn To: Caleb James DeLisle 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
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.

We track DNS disobeyers at Google, as we u= se it for load balancing (along with many other large sites).
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.
--bcaec548aa5981f48c04a9992cfe--