[154182] in North American Network Operators' Group
No DNS poisoning at Google (in case of trouble, blame the DNS)
daemon@ATHENA.MIT.EDU (Stephane Bortzmeyer)
Wed Jun 27 03:52:44 2012
Date: Wed, 27 Jun 2012 09:50:51 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Matthew Black <Matthew.Black@csulb.edu>
In-Reply-To: <ED78B1C68B84A14FA706D13A230D7B431954DB1B@ITS-MAIL01.campus.ad.csulb.edu>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Jun 27, 2012 at 03:53:17AM +0000,
Matthew Black <Matthew.Black@csulb.edu> wrote
a message of 18 lines which said:
> We believe the DNS servers used by Google's crawler have been poisoned.
[After reading the whole thread and discovering that Google was indeed
right.]
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?
