[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Dyn DDoS this AM?
- Subject: Dyn DDoS this AM?
- From: lists at eitanadler.com (Eitan Adler)
- Date: Fri, 21 Oct 2016 18:35:41 -0700
- In-reply-to: <[email protected]>
- References: <CAC1-dt=AK-f7AeeqnM4k3O0Ev+2bAbpJMObcmV7vfQp2Mf8kmA@mail.gmail.com> <[email protected]> <CAOMvUQc0eDVa=UUhUQOZbbyfQYk--oTumO8p_TE3NUMH--RnKQ@mail.gmail.com> <CAE6+G5Uxhykxp6kp2VDZNuXhceYBxtV=nzZ50qaPzc0k7ja-xw@mail.gmail.com> <[email protected]>
On 21 October 2016 at 18:12, Jean-Francois Mezei
<jfmezei_nanog at vaxination.ca> wrote:
> On 2016-10-21 18:45, david raistrick wrote:
>
>> switch too..). setting TTLs that make sense for a design that supports
>> change is also easy.
>
> Cuts both ways. Had Twitter had TTLs of say 7 days, vast majority
> wouldn't notice an outage of a few hours because their local cache wa
> still valid.
In practice TTLs tend to be ignored on the public internet. In past
research I've been involved with browser[0] behavior was effectively
random despite the TTL set.
[0] more specifically, the chain of DNS resolution and caching down to
the browser.
--
Eitan Adler