AT&T owns the actual networks that insight and mediacom use. A valid reverse lookup is usefull for security as well as management. For instance, let's say some network service requires you connect from some specific domain. Perhaps it's a sshd wrapped to allow from a specific domain. If your IP does not reverse to the correct domain, you are effectivly denied service. Even though you have not changed your IP, or forward name entry.
AT&T's IP class space is huge, because of that, it's very nice to be able to restrict authorization to a specific subset of that class. Granted idealy authorization is bound by something more tangeable like IP, however in the case of a IP block this size it's considerably safer to limit to just the specific domain.
AT&T corrected the problem last night. Also, I'm hardly bent out of shape over the asynchronous naming convention. As I said at the top of the thread, I've seen it before. My issue was with the way they treated me over the phone.
Authorization is in many ways just as critical as authentication, not having a valid reverse lookup on a network this size is problematic and unnecesary. Not to mention it's outside of RFC.
Here's a sleepy read on the issue.
RFC's 1034 & 1035
»
www.ietf.org/rfc/rfc1034.txt»
www.ietf.org/rfc/rfc1035.txt