RFC 2317 describes classless in-addr.arpa delegation. The in-addr.arpa reverse DNS name space allows for delegation at octet boundaries, /8 or /16 or /24, so DNS delegation dots match the dots in IP addresses. This worked OK for the old classful IP address architecture, but classless routing allows networks with longer prefixes, e.g. /26, which makes it tricky to delegate the reverse DNS to the user of the IP address space.
The RFC 2317 solution is a clever use of standard DNS features. If you have been delegated 192.168.144.128/26, in the parent reverse DNS zone 144.168.192.in-addr.arpa your ISP sets up CNAME records instead of PTR records for all 64 addresses in the subnet. These CNAME records point into some other zone controlled by you where the actual PTR records can be found.
RFC 2317 suggests subdomain names like 128/188.8.131.52.in-addr.arpa but the / in the label is a bit alarming to people and tools that expect domain names to follow strict letter-digit-hyphen syntax. You can just as well use a subdomain name like 128-255.144.168.192.in-addr.arpa or even put the PTR records in a completely different branch of the DNS.
For shorter prefixes it is still normal to delegate reverse DNS at multiple-of-8 boundaries. This can require an awkwardly large number of zones, especially if your prefix is a multiple-of-8 plus one. For instance, our Computer Laboratory delegated half of their /16 to be used by the rest of the University, and we are preparing to use half of 10.0.0.0/8 to provide address space for our wireless service. Both of these address space allocations would normally require 128 zones to be delegated.
Fortunately there is a way to reduce this to one zone, analogous to the RFC 2317 trick, but using a more modern DNS feature, the DNAME record (
RFC 2672 RFC 6672). So RFC 2317 says, for long prefixes you replace a lot of PTR records with CNAME records pointing into another zone. Correspondingly, for short prefixes you replace a lot of delegations (NS and DS records) with DNAME records pointing into another zone.
We are using this technique in 184.108.40.206/17 so that we only need to have one reverse DNS zone instead of 128 zones. The DNAME records point from (for instance) 255.232.128.in-addr.arpa to 255.232.128.in-addr.arpa.cam.ac.uk. Yes, we are using part of the "forward" DNS namespace to hold "reverse" DNS records! The apex of this zone is in-addr.arpa.cam.ac.uk so we can in principle consolidate any other reverse DNS address space into this same zone.
This works really nicely - DNAME support is sufficiently widespread that it mostly just works, with a few caveats mainly affecting outgoing mail servers.
For 10.128.0.0/9 we are planning to do use the DNAME trick again. However, because it is private address space we don't want to consolidate it into the public in-addr.arpa.cam.ac.uk zone. The options are to use in-addr.arpa.private.cam.ac.uk (which would allow us to consolidate 172.16.0.0/12 if we choose) or 128-255.10.in-addr.arpa which would be more similar to usual RFC 2317 style.
Example zone file for short-prefix classless in-addr.arpa delegation:
$ORIGIN 10.in-addr.arpa. $TTL 1h @ SOA ns0.example.com. ( hostmaster.example.com. 1 30m 15m 1w 1h ) NS ns1.example.com. NS ns2.example.com. 0-127 NS ns1.example.com. NS ns2.example.com. 128-255 NS ns1.example.com. NS ns2.example.com. $GENERATE 0-127 $ DNAME $.0-127 $GENERATE 128-255 $ DNAME $.128-255
With classless delegations like that your PTR records have names like 220.127.116.11-127.10.in-addr.arpa.
(I should probably write this up as an Internet-Draft but a quick blog post will do for now.)