On Mon, 5 Sep 2005, Christian Huitema wrote:
LLMNR does not create additional DNS queries.
In itself, it does not. But the operational practises it promotes very probably cause a significant increase to the number of bogus FQDN's people use, and thus have an impact on the queries to the root.
As it is, in the general case, folks either don't use hostnames like "anotherbox.somebogusdomain." in applications or they actually have a DNS server which is authoritative for that zone. That is, users often do configure bogus things like that for host names, but because the lookups don't work unless they actually have the DNS server, such use is limited. With LLMNR, such use but without the DNS server would become commonplace.
On the other hand, if you have DNS server, it might be ~OK -- there aren't additional queries to the root server under normal circumstances. (If a host moves off-link the queries typically end up in the root though.)
However, as folks have pointed out, having a lookup mechanism which can also use real FQDN's has benefits compared to just restricting to .local. The more difficult problem is being able to separate "really owned FQDN" from "invented, bogus FQDN"... while not making the problem worse by creating even more DNS traffic.
-- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf