[154155] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: DNS poisoning at Google?

daemon@ATHENA.MIT.EDU (Matthew Black)
Wed Jun 27 01:03:28 2012

From: Matthew Black <Matthew.Black@csulb.edu>
To: Michael J Wise <mjwise@kapu.net>
Date: Wed, 27 Jun 2012 05:02:49 +0000
In-Reply-To: <3C6EA8A8-B806-4B7E-9B82-68C528DFB2C1@kapu.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Q:have you consulted the logs?

Seriously? Our servers have multiple log files due to multiple virtual host=
s. Our primary domain log file on just one server has over 600,000 records =
x 3 servers.

Probably over 100,000 304 redirects in our logs.

couchtarts.com does not appear in our log files.


matthew black
information technology services
california state university, long beach

-----Original Message-----
From: Michael J Wise [mailto:mjwise@kapu.net]=20
Sent: Tuesday, June 26, 2012 9:56 PM
To: Matthew Black
Cc: nanog@nanog.org
Subject: Re: DNS poisoning at Google?


On Jun 26, 2012, at 9:35 PM, Matthew Black wrote:

> Yes, we've used the Google Webmaster Tools a lot today. Submitted multipl=
e requests and they keep insisting that our site issues a redirect. Unable =
to duplicate the problem here.

... have you consulted the logs?
If the redirect is there, it ... 1) might not be from the home page, and 2)=
 could be in ... user content?

awk '{if ($9 ~ /304/) { print $0 }}' access_log.
... or some such.
Granted, might be a storm of " " -> index.html redirects, but they should b=
e grep -v 'able in short order.
You might also look for the rDNS of the Google spider to see exactly where =
it is looking, and what it sees.

Aloha,
Michael.
--=20
"Please have your Internet License            =20
 and Usenet Registration handy..."





home help back first fref pref prev next nref lref last post