Forum Moderators: buckworks & webwork

Message Too Old, No Replies

.travel & the plugins

         

gpmgroup

8:18 am on Apr 12, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



What happens on a machine with a new.net plugin?

Which site will resolve? The new ICANN one or the new.net version?

KingMacro

5:00 pm on Apr 12, 2005 (gmt 0)

10+ Year Member



new.net dont appear to have commented on this issue as far as i can see, however they do have a more general answer in their FAQ

9. What will happen if ICANN releases a domain name extension that is identical to a New.net domain name?

We are working very hard to achieve universal resolvability of New.net domain names through a combination of ISP relationships and plug-in downloads. At the same time, we are reaching out to ICANN and its supporters to get them to understand the viability of our names and our approach and to get ICANN to add our names to the "root" servers that they operate. Should ICANN decide to introduce a domain name extension in conflict with one of our extensions and assign it to another registry, they will in fact introduce a "collision" in the name space, something they have professed wanting to avoid. If that were to happen, individual consumers and ISPs would have to choose between the ICANN version and the New.net version of the name. It is our intention to demonstrate a massive market acceptance of our names that will prevent such collisions from being introduced.

well that answers that - if both of them have the same TLD's then they will attempt to not have the same TLD's

anyone else see an official answer on this issue? personally i think people should be avoiding new.net because of issues such as these (as well as most users not being able to access any domains you buy from them) but many people did fall for this con job - i mean this slightly overpriced service that has no real use for the majority of users