[189536] in North American Network Operators' Group
AW: Verizon and Level3 DNS flush
daemon@ATHENA.MIT.EDU (=?iso-8859-1?Q?J=FCrgen_Jaritsch?=)
Wed Jun 1 14:24:58 2016
X-Original-To: nanog@nanog.org
From: =?iso-8859-1?Q?J=FCrgen_Jaritsch?= <JJaritsch@anexia-it.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Wed, 1 Jun 2016 18:24:52 +0000
In-Reply-To: <574F2692.20606@tiedyenetworks.com>
Errors-To: nanog-bounces@nanog.org
Hi Mike,
thanks for your (not so useful :)) answer ... I'm aware of things like TTL =
etc ... but the situation is that customer is receiving ~130gbit of DNS ref=
lection attack to their original DNS and that's the reason why we had to mo=
ve over to a new NS set.
I'm not allowed to tell you the customers and/or project name but I guess m=
any of you know them ... if you're reading Twitter or reddit you've probabl=
y recognized which global service is broken at the moment ...
Best regards
J=FCrgen Jaritsch
Head of Network & Infrastructure
ANEXIA Internetdienstleistungs GmbH
Telefon: +43-5-0556-300
Telefax: +43-5-0556-500
E-Mail: JJaritsch@anexia-it.com=20
Web: http://www.anexia-it.com=20
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstra=DFe 140, 9020 Klagenfurt
Gesch=E4ftsf=FChrer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U632166=
01
-----Urspr=FCngliche Nachricht-----
Von: NANOG [mailto:nanog-bounces@nanog.org] Im Auftrag von Mike
Gesendet: Mittwoch, 01. Juni 2016 20:17
An: nanog@nanog.org
Betreff: Re: Verizon and Level3 DNS flush
On 06/01/2016 10:59 AM, J=FCrgen Jaritsch wrote:
> Dear NANOGers,
>
> is there anyone from Verizon and Level3 who can help me with DNS caching =
issue? We're running a global service for a customer and we had to change t=
o NS IPs via Glue Records. At the moment at least Verizone and Level3 are c=
aching old NS records. Looking for DNS admins out there.
>
>
> Please contact me off- or on-list!
>
I totally understand the desire to just be able to go ask major=20
operators for a courtesy cache flush, but there are ways to update dns=20
and procedures to engage that can eliminate the underlaying causes of=20
same. Not that everyone, including myself, is prefect or godly (or has=20
their name in the rfc...!), but at the same time, it's a learning=20
experience being offered to you and I hope that whatever hole you shot=20
in your foot heals soon and hopefull you never have to make another one=20
like it.
Mike-
