Slashdot Mirror

← Back to Domains

Domain: superroot.net

Stories and comments across the archive that link to superroot.net.

Comments · 8

  1. maybe soon non-existant? by Anonymous Coward · · Score: 0 · on ICANN CEO Proposes Radical Changes
    they're just sealing their own fate...

    pushing more users and admins into the arms of SuperRoot and suches. They shoulda stayed happy with their fat checks. Oh well.. Aesop's dog was smarter.

  2. Re:How to see the alt root servers by scarhill · · Score: 1 · on When Worlds Collide: The New Dot-Biz And The Old

    Evidently, Superroot is what newly elected ICANN board member Karl Auerbach uses. http://www.superroot.net/how-to.html has information on how to use their alternative root.

  3. Re:How to see the alt root servers by scarhill · · Score: 1 · on When Worlds Collide: The New Dot-Biz And The Old

    Evidently, Superroot is what newly elected ICANN board member Karl Auerbach uses. http://www.superroot.net/how-to.html has information on how to use their alternative root.

  4. Re:Mozilla To The Rescue? by mutende · · Score: 3 · on When Worlds Collide: The New Dot-Biz And The Old
    You could set up a caching nameserver on your local box, e.g., dnscache (AKA djbdns) -- but even BIND will do.

    Then get yourself an alternative root zone from the SuperRoot Consortium and let your local nameserver use that one instead. For dnscache users this is as simple as replacing the contents of the .../root/servers/@ file with:

    199.166.24.1
    195.117.6.10
    199.166.24.3
    199.166.31.250
    199.166.31.3
    199.5.157.128
    204.57.55.100
    204.80.125.130
    205.189.73.10
    205.189.73.102
    207.126.103.16
    216.13.76.2
    216.196.48.66
    BIND users will please follow the instructions found here.

    Now, the new root servers provide the same service as the old ones -- i.e., they will resolve names in the .com, .org, .net, etc. TLDs, plus they will provide access to a whole bunch of alternative TLDs like, e.g., .ocean (try www.atlantic.ocean), .wine and so on. This system is plugin-compatible with the old ICANN't system (well, there's now a conflict with the .biz TLD, but who cares?).

    Go try it -- you'll like it! :-)

    // Klaus
    --

  5. Re:Mozilla To The Rescue? by mutende · · Score: 3 · on When Worlds Collide: The New Dot-Biz And The Old
    You could set up a caching nameserver on your local box, e.g., dnscache (AKA djbdns) -- but even BIND will do.

    Then get yourself an alternative root zone from the SuperRoot Consortium and let your local nameserver use that one instead. For dnscache users this is as simple as replacing the contents of the .../root/servers/@ file with:

    199.166.24.1
    195.117.6.10
    199.166.24.3
    199.166.31.250
    199.166.31.3
    199.5.157.128
    204.57.55.100
    204.80.125.130
    205.189.73.10
    205.189.73.102
    207.126.103.16
    216.13.76.2
    216.196.48.66
    BIND users will please follow the instructions found here.

    Now, the new root servers provide the same service as the old ones -- i.e., they will resolve names in the .com, .org, .net, etc. TLDs, plus they will provide access to a whole bunch of alternative TLDs like, e.g., .ocean (try www.atlantic.ocean), .wine and so on. This system is plugin-compatible with the old ICANN't system (well, there's now a conflict with the .biz TLD, but who cares?).

    Go try it -- you'll like it! :-)

    // Klaus
    --

  6. Re:Mozilla To The Rescue? by mutende · · Score: 3 · on When Worlds Collide: The New Dot-Biz And The Old
    You could set up a caching nameserver on your local box, e.g., dnscache (AKA djbdns) -- but even BIND will do.

    Then get yourself an alternative root zone from the SuperRoot Consortium and let your local nameserver use that one instead. For dnscache users this is as simple as replacing the contents of the .../root/servers/@ file with:

    199.166.24.1
    195.117.6.10
    199.166.24.3
    199.166.31.250
    199.166.31.3
    199.5.157.128
    204.57.55.100
    204.80.125.130
    205.189.73.10
    205.189.73.102
    207.126.103.16
    216.13.76.2
    216.196.48.66
    BIND users will please follow the instructions found here.

    Now, the new root servers provide the same service as the old ones -- i.e., they will resolve names in the .com, .org, .net, etc. TLDs, plus they will provide access to a whole bunch of alternative TLDs like, e.g., .ocean (try www.atlantic.ocean), .wine and so on. This system is plugin-compatible with the old ICANN't system (well, there's now a conflict with the .biz TLD, but who cares?).

    Go try it -- you'll like it! :-)

    // Klaus
    --

  7. Not to worry (was Re:SuperRoot Consortium) by DNS+Root · · Score: 1 · on If ICANN Can't, Who Can?
    Don't worry about the marketing pitch. The SuperRoot Consortium used this wording to avoid the "alternative root" label. The goal is to get the new TLDs into the ICANN root. If that fails, then there still is another, better root zone out there with all the TLDs already in - which you can use today - RIGHT NOW. :-)

    One of the new ICANN board members uses this root, and even has his own TLD in it (look for .EWE).

    Download the zone files

    FYI: There are no conflicts between the ORSC root zone and the SuperRoot Consortium root zone- they've been sync'd for the last year or so.

    --
    DNS Root
  8. SuperRoot Consortium by Brazilian+Geek · · Score: 5 · on If ICANN Can't, Who Can?

    Everyone's b*tchin' about ICANN but not many people are really doing anything about it - but in the Register article there's a link to The SuperRoot Consortium that has a proposal and is actually doing something about the TLD problems.

    I know that I'm switching over, if everybody starts using their rootservers ICANN will loose it's power and all of us will be happier. Think about it, ICANN depends on their rootservers to stay in power, use other rootservers and ICANN can't touch you.

    Like I said, I'm switching...

    --
    All browsers' default homepage should read: Don't Panic...