consolidating Reverse Zones

[Edwardo Garcia]

Hai all,

We have been given task of doing some migrations within new merger.
One of these is we have a number of reverse zones, a /19 in fact, they are
mostly GENERATE'd  for regions with fixed gw and a few other local custom
PTRs

I have played roughly with a fictitious in-addr.arpa (I play with cgnat
range since it will not affect or interfere with anyone whilst we play
around)

In our examples I have tried
zone "8-15.110.100.in-addr.arpa" {
        type master;
        file "cgnat.rev";
        notify no;
};
I also tried 8/21.110.100...  and it always complain
loading from master file cgnat.rev failed: unknown class/type

The zone file has usual header, and PTR entry are only
151.10  PTR     blue.stop.
(even tried   10.151)

I guess bind can not consolidate like this and we have to put up with a
million /24 zone files ?  I was thinking because we can do classless dele
with smaller than /24, it would work on bigger  :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20211021/93f32bc8/attachment.htm>