James Gray wrote:
[snip]
According to SORBS:
Netblock: 202.147.75.0/26 (202.147.75.0-202.147.75.63)
Record Created: Thu May 11 02:23:32 2006 GMT
Record Updated: Thu May 11 02:23:32 2006 GMT
Additional Information: [MU] Dynamic/Generic IP/rDNS address, use
your ISPs mail server or get rDNS set to indicate static assignment.
The entire 202.147.74.0/23 block has *NEVER* been part of a dynamic
range and was purchased as part of our /19 back in 1999 (or maybe
2000...before my time with this company anyway) when that address
range was first made available by APNIC. Some of the other class-C's
in our /19 have been used for a long-since-sold ISP business, but not
the 202.147.74.0/23 block.
There's only a few externally exposed MTA's in that range (although
our mail cluster is quite large). The ones really biting us on the
arse are:
202.147.74.51 (also listed on DUHL, but on a 202.147.74.0/26)
202.147.75.20
202.147.75.21
The last two don't resolve from here. make sure you have a PTR and try
delisting them individually first. use a large TTL in these PTRs. once
all your problems solved, you can switch back to whatever TTL you want.
the .51 seems ok to me, but if you can, do increase the TTLs in:
ns1.viperplatform.net.au. 436 IN A 202.147.74.80
ns2.viperplatform.net.au. 436 IN A 202.147.74.81
small TTLs resemble fast flux and may look suspicious. (besides, a small
TTL for NS records is unusual).
The idea is to maximize chances that the sorbs robot delists these IPs.
Do your own queries and whois lookups...but these address blocks are
INCORRECTLY LISTED BY SORBS and they refuse (yes, I've heard from
them) to remove them. Apparently because our inbound and outbound
MTA's don't use the same addresses! I have no idea what crack-monkey
at SORBS wrote that, but that was the response we got in relation to
our request to remove our IP's.
There may be some misunderstanding between you and them (or between you
and their robot?). I understand that this is annoying, but I think
you'll get better results by staying calm and doing some efforts until
your issues are solved.
PS. If you ever post on a sorbs mailing list, don't use the words you
used here ;-p
I hope that clears it up :)
Cheers,
James
