consolidating in-addr.arpa data

[Greg Choules]

Hi.
Although it is technically possible to do reverses on non-octet boundaries
(for example, see https://www.ietf.org/rfc/rfc2317.txt) it is a
complete pita, in my experience. Personally I would not head down that
path. Stick to /8, /16 or /24.

Cheers, Greg

On Sat, 16 Sept 2023 at 09:20, G.W. Haywood via bind-users <
bind-users at lists.isc.org> wrote:

> Hi there,
>
> On Sat, 16 Sep 2023, John Thurston wrote:
>
> > A host which auto-registers in MS DNS, creates an A in foo.alaska.gov
> > and PTR in whatever.10.in-addr.arpa. MS DNS is happy to publish those.
> >
> > But the DNS system running on BIND also has a whatever.10.in-addr.arpa
> > zone.
> >
> > So if I want to find the PTR for 13.12.11.10.in-addr.arpa, I must query
> > both DNS systems in turn. If I get NXDOMAIN from both, then I can say
> > the PTR doesn't exist.
> >
> > On each system, I'd like to be able to take the 10.in-addr.arpa data
> > from the other, compute the differences, and incorporate them locally.
> > Then I'll be able to query either system, and accept an NXDOMAIN with
> > confidence.
>
> Is there a reason not to split the /8 into two /9s or something like that?
> Then you'd have no fragmentation (at least not for this reason) and you'd
> always know who to ask.
>
> > And since writing my earlier note, I have re-located the code I think I
> > stumbled across earlier
> >
> > Tony Finch's "nsdiff"
>
> Does that mean problem replaced, if not solved?
>
> --
>
> 73,
> Ged.
> --
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20230916/6f26faf2/attachment.htm>