No DNS poisoning at Google (in case of trouble, blame the DNS)
Arturo Servin
arturo.servin at gmail.com
Wed Jun 27 13:14:12 UTC 2012
It was not DNS issue, but it was a clear case on how community-support helped.
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 at gmail.com> wrote:
> On Wed, Jun 27, 2012 at 10:50 AM, Stephane Bortzmeyer <bortzmeyer at nic.fr>wrote:
>
> 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>)?
>>
>> What was the evidence pointing to a DNS problem?
>>
>
> 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.
>
> -DR
More information about the NANOG
mailing list