NEVERMIND! (was: Seeking Google reverse DNS delegation contact)

Christopher Morrow morrowc.lists at
Thu Nov 17 02:29:09 UTC 2016

On Sun, Nov 13, 2016 at 3:57 PM, Christopher Morrow <morrowc.lists at
> wrote:

> So... actually someone did tell arin to aim these at ns1/
> I'll go ask arin to 'fix the glitch'.
the glitch got fixed, shortly after this message, but not by my/our
doing... hrm.. I see passive dns data:
count 19
first seen 2016-10-28 16:17:02 -0000
last seen 2016-11-13 08:59:50 -0000 NS NS

and after that: (overlapping that)
count 2335
first seen 2015-05-01 16:20:01 -0000
last seen 2016-11-16 21:54:01 -0000 NS NS

so.. I suspect ross digital/ noticed they made a 'mistake' and
that that 'mistake' was seen externally and .. fixed things on thier own.

With that said, it's possible (so they'll also fix this new problem):

both are 'nxdomain' from:

which seems sad, and bad.. and .. like someone has made another 'mistake' :(

rossinc, you probably want to fix this as well.

> 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 at> wrote:
>> My profuse apologies to everyone.  It seems that Google is not in fact
>> involved in any way with providing reverse DNS for the
>> IP address block.  I was deceived into believing it was by some
>> unusual trickey on the part of the spammer-controlled name servers
>> and  You can see
>> the clever deception toward the very end of the dig +trace listing
>> I posted:
>> 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
>> block.
>> Sorry for my mistake everyone.  I wasn't expecting quite this level
>> or kind of reverse DNS delegation trickery.
>> Regards,
>> rfg

More information about the NANOG mailing list