Why does LLMNR not use “.local”?
In situations where a DNS server is not available, such as in adhoc networks, it may be necessary for two machines from different companies to communicate. In these situations, an LLMNR sender may send a query for any name. This would not be possible if LLMNR only resolved names ending in the “.local” prefix. The only way that “.local” could handle this situation would be if it were appended to the searchlist, in which case any name would eventually be resolved with the “.local” suffix appended. Similarly, without placing “.local” in the searchlist a non-qualified name (e.g. “fred”) also could not be resolved on the local link. Forcing users to append “.local” to names in order to enable link local name resolution is not helpful, and requires extra overhead and training for no useful benefit.
