> It resolves because the dns sees it as it is. Just the same as
> http://www.bq--3ci46w2qaawwlyd6x52tk.com /net/org
That part is evident. It just does not jive with Ken Joy's statement that:
> Multilingual domains will not resolve in DNS at all
This is the clarification I am seeking. Is it that the names "will not
resolve at all" or that they will not resolve as anything but ASCII
characters? There is a huge difference.
-- John Keegan john@RackShare.com http://RackShare.com> From: "Merlin" <robert@chalmers.com.au> > Organization: Quantum Radio > Reply-To: "Merlin" <robert@chalmers.com.au> > Date: Sat, 2 Dec 2000 10:54:06 +1000 > To: "John Keegan" <john@rackshare.com>, "Ken Joy" <kjoy@tucows.com>, > <dev-list@opensrs.org> > Subject: Re: mlds and nameserver modification > > > But there is no way BIND will understand the Chinese character version of > that.. The native language if you like. (Chinese in this > case). > It needs that rACE decoding between it and the BIND interface. > > . > bob > --- > Robert Chalmers > http://www.quantum-radio.net.au Quantum Radio > robert@quantum-radio.net.au > http://www.inexpensivewebsites.com Inexpensive Web Sites > info@inexpensivewebsites.com > > > >>> Multilingual domains will not resolve in DNS at all...so nameserver changes >>> are largely irrelevant. We will probably allow people to change them >>> eventually, but since they don't resolve, it's not a priority. (To give you >>> some perspective, .ca changes ARE a priority, and we don't have that done >>> yet) >> >> Do you mean resolve to their native language encoding? >> >> Because I happened to come across a domain that does resolve: >> >> http://bq--3bmspgai.com/ >> >> Does this name resolve because it was not registered properly (i.e. without >> the character set bit) or is there some other explanation? >> >> -- >> John Keegan >> john@RackShare.com >> http://RackShare.com >> >> >> >
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:36:08 EDT