Thus spake "Alain Durand" <[EMAIL PROTECTED]> > On Mar 16, 2004, at 5:26 AM, Zefram wrote: > > Alain Durand wrote: > >> I too would like to see the reverse tree DNS being delegated > >> However, as there is no structure, the entire /8 to /48 address > >> space would have to be within one single zone... > > > > There is structure within the domain name segment between /8 and /48 > > -- it's a sequence of ten DNS labels, not just one. Zone cuts can be > > introduced at any level to split the job up. > > If you cut at /8, the zone is too big. if you cut at /48, there are too > many zones. > Where do you cut?
If you need AXFR and standard BIND code, then /8 /18 /28 and /38 zones are logical; just create the necessary cascading zones (if any) when new assignments are made. Yes, this creates tons of sparsely populated zones, but that's a weak point of BIND (and probably not envisioned by DNS' designers way back when). However, since there's no structure to these assignments, it seems more logical to hack up BIND or some other server to handle the unusually sparse namespace in a more appropriate manner. Presumably these servers would synchronize via means other than AXFR. S Stephen Sprunk "Stupid people surround themselves with smart CCIE #3723 people. Smart people surround themselves with K5SSS smart people who disagree with them." --Aaron Sorkin -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
