Re: [cobalt-users] Call To Arms Against New.Net

[shimi <shimi@xxxxxxxxxxxxxxxx>]

On Thu, 24 May 2001, Carrie Bartkowiak wrote:

> > link: http://www.icann.org/announcements/icann-pr15may01.htm
> >
> > Answers your question?
> 
> Nope.
> There isn't any mention of the *other* TLDs that were applied for,
> rejected, and which are now hosted by New.Net.
> That's what I'm looking for; some mention of their position regarding
> New.Net bringing out the new TLDs anyway; and what (if anything)
> they're going to do a year or two down the road when a new application
> process opens up.
> Will they make their own version of the 20 extensions New.Net is
> registering (like .xxx, .shop, .kids, .free, .club etc) and cause many
> MANY confusing scenarios (like having not one, but two different
> mydomain.shop websites/URLs)... or will they recognize the sites
> already registered at New.Net and allow the company to operate in a
> side-by-side manner with ICANN to distribute those other TLDs?
> 
> CarrieB


So I'll explain. the root servers will always run the icann approved
domains - no other dns servers will do that.

ICANN will approve gTLDs when they see fit, and will accrediate registrars
for these gTLDs.  The ones who made the fake gTLDs can *apply* but will
not necessairly be accepted.  What's sure about the whole thing is that
being an ICANN accrediated costs LOTS of money, not something I'm sure all
these companies can handle.  Besides, every regged domain (old domain
regged by those fake gTLDs) even if will be approved by ICANN to a
continued use will have to pay a fee to the root nameservers (.com/net/org
domain registrars pay $6/yr. for every domain they get into the root
nameservers)

Hopefully I made it more clear...
- shimi.