> All of the bugs cited have to do with ".local" domains. You should never use .local domains as IANA has designated this domain as a special use domain for Multicast DNS as part of IP Zeroconf and Bonjour. http://tools.ietf.org/html/rfc6762
That may be the official standard, but .local is a very common, de facto standard. Products need to be compatible with reality.
Just glancing at the RFC, is my impression correct that in February 2013, with .local already widely used for private domains, someone published an RFC appropriating the name for something else? (Could they have used a different name?) They expect the world to change their internal domains in order to accommodate their new idea?
Is there a standard for private second-level domain names? I've never seen one.
That may be the official standard, but .local is a very common, de facto standard. Products need to be compatible with reality.
Just glancing at the RFC, is my impression correct that in February 2013, with .local already widely used for private domains, someone published an RFC appropriating the name for something else? (Could they have used a different name?) They expect the world to change their internal domains in order to accommodate their new idea?
Is there a standard for private second-level domain names? I've never seen one.