The in-addr.arpa zone is delegated in much the same way as other zones: by using delegation NS records.
Accordingly, suppose you were curious as to who had the authoritative DNS server for 192.0.2.0/24. This subnet mask is divisible by 8, and so you can do:
dig in ns 2.0.192.in-addr.arpa
Your answer will contain a list of nameservers serving the rDNS zone.
IPv4 rDNS delegation is one of the few things that does not behave well with CIDR; it is only delegateable at the octet level. So, if two different parties control /25 blocks which could be aggregated into the same /24, they would have to cooperate to provide rDNS, or someone would have to operate a (very awkward) DNS server that creates individual delegation records for every single address in the /24 block.
In consequence, you will reliably find the person operating rDNS servers (which may be different from the person responsible for the IP block in whois) by successively querying IN NS for
192.in-addr.arpa (replace the documentation IP 192.0.2.1 with your target) until you find one.
That said, it is very likely that the technical contact for the IP block as shown in a whois query is the entity actually responsible for maintaining the rDNS data regardless of who is operating the rDNS authoritative nameserver.
You can also do a whois query on the delegated rDNS domain, typically:
This will give you the person who is responsible for the rDNS delegation, who is likely to be the person responsible for the rDNS itself too. This whois query is only really valid on the narrowest appropriate delegation for the block, and so if whois for the IP shows the delegation is a /23, typically the whois record will exist for the delegation at 3 octets, though it might also exist at 2 octets depending.
More information about how exactly this delegation works can be found in RFC2317, but it is very frequently done improperly or not at all, particularly outside of ARIN.
Another piece of data you can get is the SOA for the rDNS zone as queried. Simply do
dig -x 192.0.2.1
If rDNS has been set up properly, the first two strings in the SOA record returned in the authority section will indicate the authoritative nameserver and responsible person's email (replace the first