[163841] in North American Network Operators' Group
Re: Need help in flushing DNS
daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Thu Jun 20 01:33:14 2013
From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <CAPiURgUo9-GiZEp9xFdayHLc3JrT-Tdp8AkHLWgkZE3s9kMNpw@mail.gmail.com>
Date: Thu, 20 Jun 2013 01:32:17 -0400
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jun 20, 2013, at 01:30 , Grant Ridder <shortdudey123@gmail.com> =
wrote:
> Yelp is evidently also affected
Not from here.
If the NS or www points to 204.11.56.0/24 for a production =
domain/hostname, that's "bad". Yelp seems to be resolving normally for =
me.
--=20
TTFN,
patrick
> On Wed, Jun 19, 2013 at 10:19 PM, John Levine <johnl@iecc.com> wrote:
>=20
>>> Reaching out to DNS operators around the globe. Linkedin.com has had =
some
>> issues with DNS
>>> and would like DNS operators to flush their DNS. If you see
>> www.linkedin.com resolving NS to
>>> ns1617.ztomy.com or ns2617.ztomy.com then please flush your DNS.
>>>=20
>>> Any other info please reach out to me off-list.
>>=20
>> While you're at it, www.usps.com, www.fidelity.com, and other well
>> known sites have had DNS poisoning problems. When I restarted my
>> cache, they look OK.
>>=20
>>=20
>>=20
>=20
