nanog mailing list archives

Re: No DNS poisoning at Google (in case of trouble, blame the DNS)


From: Jason Hellenthal <jhellenthal () dataix net>
Date: Wed, 27 Jun 2012 09:26:05 -0400


What would be nice is the to see the contents of the htaccess file
(obviously with sensitive information excluded)

On Wed, Jun 27, 2012 at 10:14:12AM -0300, Arturo Servin wrote:

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 () gmail com> wrote:

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


-- 

 - (2^(N-1))


Current thread: