Comment 11 for bug 1382190

I started out by poking the $GENERATE directive into my reverse zone file manually:

; Zone file modified: 2014-10-21 18:24:59.654931.
; Note that the modification time of this file doesn't reflect
; the actual modification time. MAAS controls the modification time
; of this file to be able to force the zone to be reloaded by BIND.
$TTL 300
@ IN SOA maas. nobody.example.com. (
              0000000260 ; serial
              600 ; Refresh
              1800 ; Retry
              604800 ; Expire
              300 ; TTL
              )

    IN NS maas.
$GENERATE 1-100 $.0.0.10.in-addr.arpa. IN PTR no-name-yet-$.maas.
129.0.0.10.in-addr.arpa. IN PTR devoted-minute.maas.
128.0.0.10.in-addr.arpa. IN PTR dismayed-clown.maas.

This works perfectly:

graham@dodger:~⟫ dig +noall +answer -x 10.0.0.128 @10.0.0.1
128.0.0.10.in-addr.arpa. 300 IN PTR dismayed-clown.maas.
graham@dodger:~⟫ dig +noall +answer -x 10.0.0.129 @10.0.0.1
129.0.0.10.in-addr.arpa. 300 IN PTR devoted-minute.maas.
graham@dodger:~⟫ dig +noall +answer -x 10.0.0.100 @10.0.0.1
100.0.0.10.in-addr.arpa. 300 IN PTR no-name-yet-100.maas.

So, now all we need to do is have the DNSReverseZoneConfig add this for the dynamic range (I say "all we need to do"; obviously that's > 1 task, but I'll divide it up in the morning).