[154189] in North American Network Operators' Group
Re: No DNS poisoning at Google (in case of trouble, blame the DNS)
daemon@ATHENA.MIT.EDU (Arturo Servin)
Wed Jun 27 09:17:59 2012
In-Reply-To: <CAJXc8RJ63--=Fpw++bcqC4g2SsaOx4_mUcm1NnaC0P+_WX9kMg@mail.gmail.com>
From: Arturo Servin <arturo.servin@gmail.com>
Date: Wed, 27 Jun 2012 10:14:12 -0300
To: Daniel Rohan <drohan@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
It was not DNS issue, but it was a clear case on how community-support helpe=
d.
Some of us may even learn some new tricks. :)
Regards,
as
Sent from mobile device. Excuse brevity and typos.
On 27 Jun 2012, at 05:07, Daniel Rohan <drohan@gmail.com> wrote:
> On Wed, Jun 27, 2012 at 10:50 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>w=
rote:
>=20
> What made you think it can be a DNS cache poisoning (a very rare
>> event, despite what the media say) when there are many much more
>> realistic possibilities (<troll>specially for a Web site written in
>> PHP</troll>)?
>>=20
>> What was the evidence pointing to a DNS problem?
>>=20
>=20
> It seems likely that he made a mistake in his analysis of the evidence.
> Something that could happen to anyone when operating outside of a comfort
> zone or having a bad day. Go easy.
>=20
> -DR
