> 4.1 DNS Issues > AAAA and PTR records for centrally assigned local IPv6 addresses may > be installed in the global DNS. This may be useful if these > addresses are being used for site to site or VPN style applications, > or for sites that wish to avoid separate DNS systems for inside and > outside traffic.
> The operational issues relating to this are beyond the scope of this > document. > We have to be *very* careful here. If we allow PTR's to > be installed in the global DNS then globally reachable > nameservers *have* to exist for each prefix allocated. > Otherwise the problems that the AS112 project is trying to > deal with will appear here as well. > This is a long term operational cost associated with ULA-C. Well, please expand on this so we can discuss in more detail. My assumption is that some (but not all) ULA-C holders will want to be able to have PTR records. This seems operationally useful to me, for those that choose to use them and place them in the public DNS tree. Thus, we shouldn't ban it outright. That is, the question is whether the RIRs then would need to support the creation of such records for registered ULA-C owners. And help me understand how this equates to the AS112 issues. For sites that (today) get PI space and don't actually advertise it to the internet, aren't the DNS issues _exactly_ the same? Thomas -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
