consolidating Reverse Zones

Edwardo Garcia wdgarc88 at gmail.com
Fri Oct 29 00:18:15 UTC 2021


Wow, looks a right mess to be honest, might just have to leave it as is,
less aggravation.

Hard to understand why in 2021 almost 2022, we can't do something so simple
in dns

On Thu, Oct 21, 2021 at 9:49 PM Tony Finch <dot at dotat.at> wrote:

> Edwardo Garcia <wdgarc88 at gmail.com> wrote:
> >
> > 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  :)
>
> It is possible! The basic idea (very briefly) is:
>
> With classless reverse DNS for prefixes longer than /24, you need a CNAME
> in the /24 zone pointing at each address in the classless zone.
>
> For shorter prefixes, you need a DNAME in the /16 zone pointing at each
> /24 in the classless zone.
>
> There are some documents explaining how we use this trick in production
> at https://www.dns.cam.ac.uk/domains/reverse/ with links to the less
> Cambridge-specific explanations in the last two paragraphs of that page,
> viz:
>
> https://www.dns.cam.ac.uk/domains/reverse/technical.html
>
> https://tools.ietf.org/html/draft-fanf-dnsop-rfc2317bis
>
> Tony.
> --
> f.anthony.n.finch  <dot at dotat.at>  https://dotat.at/
> Lundy, Fastnet: Northwest 4 or 5, occasionally 6 in Lundy. Rough or
> very rough, becoming moderate or rough, then moderate later. Showers.
> Good, occasionally moderate.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20211029/838f5e7b/attachment.htm>


More information about the bind-users mailing list