> Where is this "NEW" User Guide?? >How new is it???
New enough to contain the most up to date information about multilingual name resolution. >Unless something has > drastically changed in the last 2 months of which there has been no > announcement, they do not work. They work exactly as I described they would in previous announcements citing the exact same New User Guide that we're talking about here. > I have been over this multiple times > with the people at Tucows, and everybody keeps saying they work, but > they DO NOT work. They work as well as they possibly can given the nature of the initiative. I'm pasting in the instructions for your convenience: We are currently in Phase 2. In order to test your multilingual name registration during Phase 2, you must set up the zone file for your domain as follows: multinlingualname.mltbd.com IN A IP.ADD.RE.SS bq-qbdfecssd.mltbd.com IN A 123.321.123.321 NOTES: The file must use either the mltbd.com, mltbd.net or mltbd.org zones, depending on whether your multilingual name is a .com, .net, or .org. Once that's done, web surfers with IE 5 or greater who enter native characters into the URL window and hit 'enter' will be taken to the site specified in the DNS> > If you want to type the race code into the url window, and you define > that as working then ....... I do not. Are you sure you've followed the instructions correctly? >, but if you want to type Japanese (or > other native) characters into the url window and have them resolve, it > certainly does not work. It certainly does. I've seen it myself. >I with > People at Tucows say they do, but I have not > been able to get them to resolve from Japan no matter what version of IE > I use or what OS. This is a completely different statement that "it certainly does not work". > As I understand it, Microsoft wants to do it their own way, Verisign > wants to do it their own way, and neither of them are willing to budge > until ICANN defines a standard, which is pushing on a year and a half > now. All of this may be true, but it does not stand in the way of the fact that correctly set up DNS with the correct browser will result in a 'working solution' for at least some people. > As it stands, I would bet that in about 2 months, 90 to 95% of our > Multilingual Domain name registrants are not going to renew because they > are disenchanted with it. This would not surprise me. The six month extension on the names was meant to placate these people; after speaking with Verisign, I got the impression that we could all expect some movement on this in the next couple of months, but they are loath to commit to timeframes because the quest for a 'standard' does complicate the issue. ? IMHO, Verisign as well as Tucows and others, > should not charge any further renewal fees until the MDNs correctly > resolve in the actual root dns and not in some half brained work-around > to try and pull a little more money out of people. We will charge resellers for renewals as long as Verisign is charging us for renewals; of course people who don't believe the process will ever bear fruit are free not to renew; I can even lobby Verisign with your arguments, but I can almost guarantee that I won't sway them....sure they are interested in running an industry leading 'test initiative', but more basically, they are interested in making money. Thanks, Ken > > John Spohr > I.S. International, Inc. > Tokyo, Japan > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Ken Joy > Sent: Tuesday, March 05, 2002 5:03 AM > To: John Keegan; [EMAIL PROTECTED] > Subject: RE: Multilingual domains > > 1. The names will resolve if you set up your zone files according the > instructions in the New User Guide AND the 'surfers' are using IE 5.0 or > higher. > > 2. Verisign will be switching to a new encoding standard *sometime* in > the > next few months. When they do, we will deal accordingly (and it should > not > affect how Resellers register multilingual domains). > > 3. I have no idea about the 'rest' of the schedule (which I see as the > move > to a standard that is NOT depenadant on browser plug ins) in terms of > timelines. However, I'll look into it. > > Thanks! > > Ken > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of John Keegan > > Sent: Monday, March 04, 2002 3:00 PM > > To: [EMAIL PROTECTED] > > Subject: Multilingual domains > > > > > > What is the current status of Multilingual domains? What "phase" of > the > > experiment are we now in andhow usable are the domains currently? > > > > -- > > John Keegan > > [EMAIL PROTECTED] > > http://RackShare.com > > > > > >
