consolidating Reverse Zones

Mark Andrews marka at isc.org
Fri Oct 22 00:43:50 UTC 2021



> On 21 Oct 2021, at 18:33, Edwardo Garcia <wdgarc88 at gmail.com> wrote:
> 
> 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

Remove the white space from the front on the record on this indicated line.

“ 151.10 PTR blue.stop.” is not the same as "151.10 PTR blue.stop.”

Leading white space is “take the name from the previous record”.

> 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  :)
> 
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
> 
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka at isc.org



More information about the bind-users mailing list