Quote:
|
Originally Posted by adoptabledomains I would guess the plugin would still override the real TLD since it sends lookups to different DNS servers for those domains. However, I would also bet the ISP's who have made new.net domains available would change their DNS servers to see the real ones. I think this number far outnumbers the plugin users. |
I tested the new.net plugin on a computer that its DNS configured to resolve another alternate root (new root formally pacific root) that also has a .travel TLD and the result was that the new.net plugin would still override the "real TLD" in the DNS. The details are here:
http://www.finee.com/travel_tld.htm
As to the number of Internet users that have the new.net plugin installed I do not know. New.net claims "174,661,619 New.net enabled Internet users worldwide" and I would not be surprised if a significant proportion of these are using the plugin.
Something tells me that new.net will not be another ARNI .biz and the registrants in the ICANN .xxx and .travel will need also the new.net names if they want universal resolution of their domains.