[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Dyn DDoS this AM?
- Subject: Dyn DDoS this AM?
- From: george.herbert at gmail.com (George William Herbert)
- Date: Fri, 21 Oct 2016 18:43:58 -0700
- In-reply-to: <CAF6rxgk9E1=f1Dz+yMOqMkvUbjX3Jqwxisu28M1YAs7_kYLonQ@mail.gmail.com>
- 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]> <CAF6rxgk9E1=f1Dz+yMOqMkvUbjX3Jqwxisu28M1YAs7_kYLonQ@mail.gmail.com>
> On Oct 21, 2016, at 6:35 PM, Eitan Adler <lists at eitanadler.com> wrote:
>
> [...]
>
> 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.
Yes, but that it can be both better and worse than your TTLs does not mean that you can ignore properly working implementations.
If the other end device chain breaks you that's their fault and out of your control. If your own settings break you that's your fault.
Sent from my iPhone