[154183] in North American Network Operators' Group
Re: No DNS poisoning at Google (in case of trouble, blame the DNS)
daemon@ATHENA.MIT.EDU (Daniel Rohan)
Wed Jun 27 04:09:04 2012
In-Reply-To: <20120627075051.GA11061@nic.fr>
From: Daniel Rohan <drohan@gmail.com>
Date: Wed, 27 Jun 2012 11:07:56 +0300
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Jun 27, 2012 at 10:50 AM, Stephane Bortzmeyer <bortzmeyer@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
