[192700] in North American Network Operators' Group
Re: NEVERMIND! (was: Seeking Google reverse DNS delegation contact)
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Sun Nov 13 18:59:28 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <9287.1478844315@segfault.tristatelogic.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Sun, 13 Nov 2016 15:57:19 -0800
To: "Ronald F. Guilmette" <rfg@tristatelogic.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
So... actually someone did tell arin to aim these at ns1/2google.com...
I'll go ask arin to 'fix the glitch'.
thanks!
-chris
(sometimes people do this, I have no idea why... perhaps they just like
broken ptrs?)
On Thu, Nov 10, 2016 at 10:05 PM, Ronald F. Guilmette <rfg@tristatelogic.com
> wrote:
>
>
> My profuse apologies to everyone. It seems that Google is not in fact
> involved in any way with providing reverse DNS for the 204.8.136.0/21
> IP address block. I was deceived into believing it was by some
> unusual trickey on the part of the spammer-controlled name servers
> ns1.saversagreeable.com and ns2.saversagreeable.com. You can see
> the clever deception toward the very end of the dig +trace listing
> I posted:
>
> http://pastebin.com/raw/VNwmgMHh
>
> It seems those clever rascal spammers tried to implicate Google's
> name servers, but it is only their's which are giving out the
> reverse DNS which suoorts their snowshoe spamming efforts in the
> 204.8.136.0/21 block.
>
> Sorry for my mistake everyone. I wasn't expecting quite this level
> or kind of reverse DNS delegation trickery.
>
>
> Regards,
> rfg
>
