Brian E Carpenter wrote: > Scott, you say > >> In a situation like this, I need to be able to resolve PTRs for hosts >> using my neighboring networks' ULA space > > Why do you need to do this?
The need can be seen, but the big question is: why does one need it in the *global* root. If one is in a non-Internet-connected setup, you will have to also setup DNS for the, IMHO way more important, forward zones. If one can manage that, then setting up the reverse is just an extra line in the config. When one argues "yes but I don't want split DNS and it needs to be in the global DNS", then simply don't opt for *local* addresses. Either the ULA-C space is *local* or it is *global*. When it is global, then you need what the RIR's dub PI. If you can't get PI for your use, then talk to the RIR's and define a new policy there. One thing that can be accomplished by the ULA-C draft is to update the ULA draft, deprecating the L/G bit, making that bit part of the random pool (letting folks simply select it themselves) and defining that the reverse in the global root should point to the AS112 servers. Greets, Jeroen
signature.asc
Description: OpenPGP digital signature
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
