In message <[email protected]> Michael Richardson writes: > >>>>> "Brian" =- Brian E Carpenter <[email protected]> writes: > Brian> Correct, but the name is unambiguous, which IMHO is a MUST > Brian> property for anything that looks like an FQDN. We have to > Brian> live with .local but it should be just a nasty memory like > Brian> 10.0.0.0/8 fifty years from now. > > Brian> I would suggest instructing IANA to reserve all TLD strings > Brian> that start with "local" and using something like > Brian> .local-fd952a92a67d to name the homenet domain. It's only a > Brian> convenience to use a ULA prefix; it's simply a unique string > Brian> that the CPE needs to generate anyway, but it has no > Brian> significance beyond that. > > huh, you want to do it that way? > Why not fd952a92a67d.local? > > I'm asking for clarification, not disagreeing. > > > Michael Richardson <[email protected]>, Sandelman Software Works
I'd prefer mDNS returns a mapping of printer3.local to a CNAME printer3.fqdn and DNS returns a mapping of printer3.sitelocal (or localsite if you prefer) to CNAME printer3.fqdn. In both cases, if there is a subdomain delegated by the provider, then fqdn is that subdomain, and if no subdomain has been delegated, then the fqdn is of the form <ula>.local (ie: fd952a92a67d.local in your example). An application can (though none today do, cups for example could be changed) obtain the query results using the partial domain name (ie: printer3) and gethostbyname2 to get an address and then use gethostbyaddr to do an rDNS lookup to get the FQDN if printer3.sitelocal was first in the DNS search path. If the mapping from printer3.sitelocal were to change, the user could be given a choice to use the new printer3.sitelocal or use the old one through the FQDN. Multiple mappings of printer3.sitelocal could be retained, such that printer3 yielded a list each time a request was made to print using this unqualified name. Of course that would mean rDNS would have to work. Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
