I've had similar problem at SpeakEasy. They still don't have a reverse-DNS
clue.
http://www.mhsc.com/recovery.htm
None of the DSL ISPs can do larger than /27 anymore, even when they're
ILECs. Anything less than a /24 can't be SWIP'd and if you don't control
your in-addr.arpa entries you don't control your domain and have no
security.
* Roeland Meyer <rmeyer@mhsc.com> [20010513 13:45]:
None of the DSL ISPs can do larger than /27 anymore, even when they're
ILECs.
What does being an ILEC have to do with layer 3 routing?
'sides there are plenty of DSL ISPs that offer larger than a /27. Heck, I
count some of them among my clients who consist primarily of smaller
regional players. If you are looking for more major player examples that
offer larger IP blocks:
* MegaPath
<URL:http://www.megapath.net/> (see Support -> IP Request Form)
* PacBell/SBC
<URL:http://public.pacbell.net/dedicated/dsl/dsl_business.html>
How hard have you looked, Roeland?
Anything less than a /24 can't be SWIP'd and if you don't control
your in-addr.arpa entries you don't control your domain and have no
security.
This is FUD. For example, look up "63.201.8.120". That sure looks like a
/29 to me. Hell, that's even being done by an ILEC owned ISP. 
In fact,
ARIN (and other regional registries have similar policies) encourage SWIP
reassignments for anything up to and including /29. An NSP who has to
justify its requests for IP space (read: any) knows how much easier and
quicker the process is made when they have everything SWIP'd already.
<URL:ftp://ftp.arin.net/pub/swip/swipinstruction.txt>
As to controlling your reverse delegation, if your IP block is less than a
/24 how often do you _really_ need to change your reverse? If the answer is
not often you are losing nothing by having your upstream handle it for you.
If you still want control of it, convince your upstream to implement
RFC2317 (if they haven't already):
<URL:http://www.rfc-editor.org/rfc/rfc2317.txt>
As to trusting reverse nameservice records for security, well, that's your
choice not mine..
-jr
Actually, ARIN mandates that any ISP MUST SWiP any block shorter than /28.
Perhaps they just don't want to take the time to change the reverse dns
servers in your SWiP templates, and/or they don't want to have to deal with
adding cname records for all of your ip's in their in-addr zones. I can't
even get INAP to give me direct control over my /20 because my blocks are a
part of their larger blocks, and it's too difficult for them (so they say)
to edit their bind servers.
It seems apparent that rdns is not an important issue to ISP's nowadays. To
be honest, it's not important to mine either. We won't give someone control
of their reverse dns. It's too time consuming and resource intensive to
handle for hundreds of clients. I think few people realize the limited
bottom line involved in running a DSL ISP. There isn't much room to spend 20
minutes setting up some guy's rdns zones when you're not even making a
profit off of his line. 
We all want to keep clients happy, but there must be a limit.
Hunter Pine
Vice President, Network Operations
hunter@compuhelp.com
Correction, any block shorter than a /29, not a /28 must be SWiPed if you
ever want another IP block from ARIN again.