AT&T / Verizon DNS Flush?
blake at ispn.net
Wed Apr 16 16:50:56 UTC 2014
Seems like the DNS protocol already addresses this issue with TTLs. The
issue is that people sometimes regret the TTLs they chose (or their
service provider chose for them). Any reason registrars commonly choose
a 2 day TTL? Would they be just as well off with a 1 day TTL (my guess
is that they would)?
Hank Nussbacher wrote the following on 4/16/2014 11:32 AM:
> At 10:21 16/04/2014 -0600, Steven Briggs wrote:
> Been discussed and nothing has been done:
> Will keep happening until someone decides to act.
>> Yeah...I know. Unfortunately, the domain was "mishandled" by our
>> registrar, who imposed their own TTLs on our zone, THEN turned it
>> back over
>> to us with a 48HR TTL. Which is very bad.
>> I really appreciate all of your help, guys!
>> On Wed, Apr 16, 2014 at 10:14 AM, Laszlo Hanyecz
>> <laszlo at heliacal.net>wrote:
>> > The generally accepted and scalable way to accomplish this is to
>> > your freshness preferences using the SOA record of your domain. It
>> > be pretty tricky to make this work with a swivel chair type system for
>> > every domain and host on the internet. You would have to contact
>> > user and ask them to invalidate the caches, after asking their
>> > server operator to do the same.
>> > -Laszlo
>> > On Apr 16, 2014, at 6:15 AM, Steven Briggs <stevenbriggs at gmail.com>
>> > > Hello,
>> > >
>> > > Not sure where to point this... I was wondering if anybody knows an
>> > inroad
>> > > to reach AT&T and Verizon systems people to flush their caches for "
>> > > proofpoint.com"?
>> > >
>> > > Any help is greatly appreciated!
>> > >
>> > > Steven Briggs
>> > > á§
More information about the NANOG