127.0.0.2

[Mike Black]

Yup -- you're right.
It's dorkslayers.com which went away and now returns 127.0.0.2 for the host address.

Looks like upgrading from SpamAssassin 2.50 to 2.60 fixed the problem.  I imagine 2.60 removed dorkslayers from the checks.
Thanx....

----- Original Message ----- 
From: "Barry Margolin" <barry.margolin at level3.com>
Newsgroups: comp.protocols.dns.bind
To: <comp-protocols-dns-bind at isc.org>
Sent: Wednesday, October 08, 2003 10:40 AM
Subject: Re: 127.0.0.2


> In article <bm15hc$jv9$1 at sf1.isc.org>, Mike Black <mblack at csi-inc.com> wrote:
> >All of a sudden, on Sep 29 05:03:30 (EDT) I started seeing named kicking
> >out UDP requests to 127.0.0.2
> 
> Someone probably assigned this address to a nameserver that their domain is
> delegated to, e.g.
> 
> baddomain.com. IN NS badserver.baddomain.com.
> 
> badserver.baddomain.com. IN A 127.0.0.2
> 
> If you dump the cache of your nameserver you can probably find it.
> 
> -- 
> Barry Margolin, barry.margolin at level3.com
> Level(3), Woburn, MA
> *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
> Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.