That is correct - and it almost makes sense. Further to that, it is likely
that the bq-- will change to something else...(I'm holding out for rr-- ;)
<
< You are correct since when mutil-lingual DNS is supported the
< language won't
< be set and thus will (this is a guess based on current discussions with
< people who are involved in this) resolve as an english domain
< rather than a
< foreign language and thus won't resolve to the foreign domain
< correctly. The
< exception might be if you registered a domain already re-decoded
< by RACE and
< set the language to none (which is english then by default) and
< pointed it
< to the same place.
<
< Does any of this make any sense the way I am trying to describe it?
<
< Tim Jung
< System Admin
< Internet Gateway Inc.
< tjung@igateway.net
<
<
< ----- Original Message -----
< From: "Charles Daminato" <chuck@tucows.com>
< To: "John Keegan" <john@rackshare.com>
< Cc: <dev-list@opensrs.org>
< Sent: Friday, December 01, 2000 8:28 PM
< Subject: Re: mlds and nameserver modification
<
<
< > Many persons have registered names in the "regular" name space already
< > RACE encoded - so their regular ASCII versions (like you see below) are
< > there...
< >
< > However - these will not (supposedly) work properly with decoded MLDNs
< > if/when the VeriSign root actually starts resolving.
< >
< >
< > Charles Daminato TUCOWS Product Manager (ccTLDs) chuck@tucows.com
< >
< > On Fri, 1 Dec 2000, John Keegan wrote:
< >
< > > > 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