The / is not forbidden, might be technically true, but ... I have more often seen a delegation in the style of an ip-range like 0-63. I actually expected that in the BCP.
The forward zone is a neat option, but it needs more coordination with the parent if not all of your addresses are in the same forward zone. Anyway, maybe some more people can join in and tell what they are using? Thanks! /Ulrich On 2026-05-13, 13:21, "Peter Eckel via dns-wg" <[email protected] <mailto:[email protected]>> wrote: Hi, I did some work on RFC 2317-based delegation in the course of the development of NetBox DNS <https://github.com/sys4/netbox-plugin-dns> <https://github.com/sys4/netbox-plugin-dns>> which supports RFC 2317 delegation. Yes, the RFC is essentially correct, and using a / in a label is not forbidden either. You can do that, which doesn't mean that you should :-) Citing from https://datatracker.ietf.org/doc/html/rfc2317#section-4 <https://datatracker.ietf.org/doc/html/rfc2317#section-4>: > The examples here use "/" because it was felt to be more visible and > pedantic reviewers felt that the 'these are not hostnames' argument > needed to be repeated. We advise you not to be so pedantic, and to > not precisely copy the above examples, e.g. substitute a more > conservative character, such as hyphen, for "/". In fact an RFC 2317 reverse zone is nothing but a normal zone and does not need to follow the normal delegation scheme for .in-addr.arpa. You can even insert your PTR records in your forward zone, as long as you poing the CNAMEs in the parent zone at the right target. Best regards, Pete. ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/dns-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
