We should also note that the issue arises in part because a
very widely deployed web browser (hint: Internet Exploder) emits
invalid DNS requests that use UTF8 -- and that any such {browser,
DNS resolver} implementation is badly broken and needs to get
patched immediatley by the implementer (Microsoft) so that the
{browser, DNS resolver} fully complies with all DNS standards.
Actually, is this true? Where in the DNS specs is it defined what to
do when an application wants to do a DNS lookup for a non-ascii
string? I may be wrong, but I thought that this is an area of the
standards where things are somewhat underspecified.
If one asserts that things are so underspecified that the MS