On 06/18/2014 11:07 AM, Jim Reid wrote: > On 18 Jun 2014, at 15:45, Michael Orlitzky <mich...@orlitzky.com> > wrote: > >> Nitpick: the ".local" TLD is reserved by RFC 6762, ".invalid" may >> be a better long-term choice. > > I'll raise you another nitpick. .invalid is reserved by RFC6761 and > in the IANA registry of Special-Use Domain Names, just like .local:
Indeed, thanks for that. I hadn't seen it before. The problem that arises is that you must choose a reserved name, otherwise you may find one day that your made-up name belongs to somebody else. RFC2606 reserved ".test", ".example", ".invalid" and ".localhost" but didn't specify how they should be handled. Among those, I interpreted ".invalid" to have the closest meaning to "internal only." Now, RFC6761 says that resolver libraries SHOULD immediately return a negative response for ".invalid" queries. So I'm not sure what we're left with. We have encountered problems with ".local" and Apple gizmos as you mentioned. And personally I don't think I could stand to see ".test" on the end of a hostname for all eternity. But from RFC6761, that seems like the best option.
