Slashdot Mirror

← Back to Domains

Domain: i-dns.net

Stories and comments across the archive that link to i-dns.net.

Comments · 6

  1. Really? by mattr · · Score: 1 · on China Prepares to Launch Alternate Internet
    A new root system would be nasty but on the other hand if you are going to aim nukes at the guys running the network you might as well build your own network too just in case no?

    But it may not be as bad as all that. Not that I think it is a great idea, but Japan for example is starting domain naming in Japanese characters (hiragana and katakana alphabets, or kanji which are basically Chinese characters). So you need UTF-8 and Japanese font display and input support just to type in the domain name.

    Check out this page which says it is ICANN authorized plus it offers .jp domains in kanji ("IDN multilingual domains") side by side with English ones.

    I also note that i-dns.net in California supports root domains and they provide soft keyboard java applets to input them. I don't know anybody using them, though a 2000 press release mentions a couple well known companies in Japan, but I can see that the top selection in the dropdown menu (read as "koushi" or public in Japanese, though it is really Chinese which I can't read) is possibly what they will use for ".com" for example the Japanese versions use "kaisha" (company) and "netto" (net) as .com and .net equivalents it seems.

    I found a 2002 Internet Draft from JPNIC on this sort of thing. It seems to me the biggest problem is that you have to be able to read a language to access an address written in that language. May be useful for old folks but at present it seems to be quite unpopular in Japan.

  2. Some tech details, and a question by nstrom · · Score: 5, Interesting · on China Locks in its Net-Citizenry

    These LGA people claim to require a browser plugin to use these Chinese domain names. However, it just seems that they're implementing the names using punycode and some new (presumably non ICANN-approved) TLDs.

    For example, the domain name "." resolves via punycode to xn--eqro3ot1fkxx.xn--55qx5d. Now we can check this domain via whois:

    $whois -h whois.i-dns.biz xn--eqro3ot1fkxx.xn--55qx5d

    i-DNS.net WHOIS Server Version 1-2-0

    This service may be used to query the availability of
    multilingual domain names. Please visit http://www.i-DNS.net/
    for more information about multilingual domain names.

    For help with the i-DNS.net WHOIS service, type 'HELP'.

    Domain ID: D1148313-IDNS
    Domain Name (Native): .
    Domain Name (ACE): xn--eqro3ot1fkxx.xn--55qx5d
    Created On: 14-Nov-2004 19:58:54 GMT
    Last Updated On: 02-Mar-2005 06:12:50 GMT
    Expiration Date: 14-Nov-2006 19:57:30 GMT

    ... [snipped to get past line-length filters] ...

    Name Server: ns1.i-dns.biz
    Name Server: ns2.i-dns.biz
    and we can actually resolve this name if we use the right DNS server:

    $dig xn--eqro3ot1fkxx.xn--55qx5d @ns1.i-dns.biz

    ; > DiG 9.2.2 > xn--eqro3ot1fkxx.xn--55qx5d @ns1.i-dns.biz
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;xn--eqro3ot1fkxx.xn--55qx5d. IN A

    ;; ANSWER SECTION:
    xn--eqro3ot1fkxx.xn--55qx5d. 86400 IN A 203.81.44.27

    ;; AUTHORITY SECTION:
    xn--eqro3ot1fkxx.xn--55qx5d. 86400 IN NS ns1.universal-names.com.
    xn--eqro3ot1fkxx.xn--55qx5d. 86400 IN NS ns2.universal-names.com.

    ;; ADDITIONAL SECTION:
    ns1.universal-names.com. 117755 IN A 203.81.44.40
    ns2.universal-names.com. 117774 IN A 203.81.44.27

    ;; Query time: 821 msec
    ;; SERVER: 203.81.44.40#53(ns1.i-dns.biz)
    ;; WHEN: Tue Apr 26 19:49:06 2005
    ;; MSG SIZE rcvd: 148
    The question raised here then is the following: why use a browser plugin at all if all is needed is to configure the user's DNS resolver to consult alternate root servers for the new TLDs? The paranoid conspiracy theorist in me suggests spyware, or something else that's not quite kosher.

  3. .LA is a SCAM. by SlashChick · · Score: 5, Informative · on Los Angeles Gets Own TLD
    Oh, man. .LA domains. Where do I begin?

    Some background: .LA has been around for several years. Here is one of the initial announcements, dated February 2001.

    I have a client who bought one of the initial .LA domain names. He paid $150 to the then-registrar of .LA domains for 5 years of service.

    Last December, he got a notice stating that the contract between Laos (the official holder of .LA) and the domain registration company had expired. The letter said, in part, "On 11 December 2002 ICANN announced its decision to re-delegate the ccTLD .la to the Lao Government, specifically the Lao National Internet Committee (LANIC). DotLA and Sterling were not aware that this change was being contemplated by ICANN or IANA, and we were not contacted by ICANN/IANA for our comments either before or after ICANN made its decision."

    The letter goes on to explain that ICANN changed the official name servers for .LA to an as-yet-unnamed company. My client's domain name continued to work, but he knew he was borrowing time.

    Suddenly, Dreamhost (the current .LA registrar) waltzed in and paid a handsome sum of money to become the official .LA registrar. Of course, they chose not to honor my client's 5-year registration, and demanded that he pay MORE money or have his domain name cease to work.

    This has been a frustrating 6 months. My client has since registered a .biz domain, which is controlled by ICANN and not by any specific company. This means that there is no "official" registrar for .biz domains, and that there aren't going to be any disputes over who owns the TLD.

    After the $150 that has been wasted by my client for a "5-year" registration, what's to say that Dreamhost won't also get into a dispute and dump .LA completely? At that point, all current .LA domain name holders would be in the same position as my client -- forced to change their web address because the company can't get it together, and losing money in the process.

    .LA is a mess. I would not recommend registering a .LA domain until the whole mess stabilizes a bit.

  4. i-dns.net by Cmdr.+Marille · · Score: 2 · on China Snubs Verisign In Domain Tussle

    someone at cnet pointed to a site called i-dns.net"
    what they have listed under tech might actually be quite insightfull(even thought not technical) and may also prove the point that china can't actually block those other registration companies.

  5. Re:Death to Pronounciation by David+A.+Madore · · Score: 2 · on DivX ;-) Deux Update

    Wait 'till they start using Unicode characters which you don't even understand or know how to type.

    Like "ACME" (if your browser supports Unicode and you have the right fonts you should see a smiling face after "ACME"), or "Esterica" or "Fbar" whatever. (Not to mention that artist whose name used to be "Prince" and who changed it to some unspeakable hieroglyph.)

    Then, with I-DNS they can even have domain names with their weird and untypable characters. Yuck.

  6. Internationalized Domain Names by jseng · · Score: 1 · on ICANN Plans Non-English Character Domain Testbed

    For those who are interested in IDN, here are some URL.

    IETF IDN WG
    http://www.i-d-n.net/

    NSI Registry Testbed
    http://www.nsiregistry.com/

    i-DNS.net (Technology Provider for NSI ML.com testbed)
    http://www.i-DNS.net/

    Multilingual.COM Promotion
    http://we-multilingual.com/