This seems to be covered by RFC3490 (e.g.
ftp://ftp.rfc-editor.org/in-notes/rfc3490.txt)

There's a few notable things in there

IDNA allows the graceful introduction of IDNs not only by avoiding
   upgrades to existing infrastructure (such as DNS servers and mail
   transport agents), but also by allowing some rudimentary use of IDNs
   in applications by using the ASCII representation of the non-ASCII
   name labels.


The IDNA protocol is contained completely within applications.  It is
   not a client-server or peer-to-peer protocol: everything is done
   inside the application itself.  When used with a DNS resolver
   library, IDNA is inserted as a "shim" between the application and the
   resolver library.  When used for writing names into a DNS zone, IDNA
   is used just before the name is committed to the zone.



Which makes sense to me...  If the DNS servers / clients had to change
in order to support this, then it would only be usable by a very, very
small subset of the internet.

It looks like, while it would be helpful to have the resolver libraries
provide cover functions, the intent from the RFC is for the application
to handle the IDNA "toASCII" conversion before handing the ASCII string
off to the standard resolver / DNS server library functions.


	Robert.



-----Original Message-----
From: Cabel Sholdt [mailto:csholdt@zebra.com] 
Sent: Tuesday, July 01, 2008 4:06 PM
To: technology-networking
Subject: Support for International Domain Names?

I am curious as to whether or not the QNX DNS client/library for IPv6
supports International Domain Names? This was asked of me and I couldn't
find an answer in the documentation (I am still going through it
though).

If it is useful, more information about IDN can be found here:
http://www.icann.org/topics/idn/

Thanks for the help,
Cabel

_______________________________________________
Technology
http://community.qnx.com/sf/go/post9888