nanog mailing list archives

Re: SORBS on autopilot?


From: Larry Smith <lesmith () ecsis net>
Date: Mon, 11 Jan 2010 10:01:11 -0600

On Mon January 11 2010 09:48, Ken Chase wrote:
Anyone got some pointers on how to get off SORBS' Dynamic IP lists?

We've followed their RFC proposed static reverse DNS assignment naming and
all elements of their FAQ.

We are not spammers. The /24 in question isnt listed on any RBLs except
SORBS DUL.

We've submitted requests in various different formats, but get a robot
reply and -ENOJOY.

We've even had our upstream that is listed at the RIR as managing the
supernet of our BGP announced prefixes submit requests to delist for the
/24, but we are only ever replied to by a robot that lists 67.196.137.0/24
as dynamic except .163 (somehow manually excluded from their db, I think
when they werent adrift in years past). Our upstream's techs are also at a
loss now and suggested I seek arcane clue amongst the sages here.

Pointers appreciated.

/kc

Hmmm, probably something to do with your "reverse" naming convention:

host 67.196.137.1
1.137.196.67.in-addr.arpa domain name pointer 
H1.C137.B196.A67.tor.colo.heavycomputing.ca.

host 67.196.137.163
163.137.196.67.in-addr.arpa domain name pointer sizone.org.

host 67.196.137.16
16.137.196.67.in-addr.arpa domain name pointer 
H16.C137.B196.A67.tor.colo.heavycomputing.ca.

host 67.196.137.162
162.137.196.67.in-addr.arpa domain name pointer 
H162.C137.B196.A67.tor.colo.heavycomputing.ca.

IP 67.196.137.163 appears to actually have a "name" and everything
else has Hnnn.C137.B196.A67.tor.colo.heavycomputing.ca (where nnn
is the fourth octet IP).

-- 
Larry Smith
lesmith () ecsis net


Current thread: