<<<
Chronological Index
>>> <<<
Thread Index
>>>
[ga] FTC Really should take action against ICANN and Neulevel for Failing to provide proper disclosures to consumers
I get two of three of these a week. The FTC really ought to take action against ICANN and Neulevel
for failing to require their retailers to disclose to the public that their version of .BIZ is a collider and is
not universally visible. There are so many hucksters out on the internet these days, you know :-)
-- Reply to email sent to info at adns dot net---
There isnt any problem here on our end.
You see, there are two different versions of .BIZ - the original one and the colliding one that ICANN created.
Each version of .BIZ has different registrants in it.
The fact that your traceroute shows 199.5.157.11 as an address for your .BIZ says 2 things:
1. That no one has goldenpark.biz registered in the original version of .BIZ, which means you must
have registered your .BIZ in the colliding (ICANN/Neulevel) version.
2. That whatever machine that you are using to do the traceroute is using an Inclusive Namespace
nameserver that recognized the original and authentic version of .BIZ and not the pretender
version that ICANN and Neulevel created.
The only thing I can tell you now is to check your name servers and make sure you are using
nameservers which point to the ICANN/USG root. Of course, this will shut you off from the thousands of other toplevel
domains that exist out there, but such is the mess that ICANN created.
199.5.157.11 is the address of the catchall website for any non-registered .BIZ domains in the original
version of .BIZ. It will also catch any queries for websites that don't yet have A-Records. You can't ping
or traceroute because we disallow that traffic onto our network. You can however, put 199.5.157.11 in
your browser.
I don't know what to tell you, except that ICANN/Neulevel sold you a "Bill of Goods" if they represented to
you that your domain would be universally visible since they knowingly created a duplicate version of .BIZ and
they knew that the Inclusive Namespace, used by up to 30% of the internet, would not be able to see any domains
registered in their version of .BIZ. The Original and Authentic version of .BIZ existed long before they created
a duplicate (since 1995, to be exact). I suggest you ask your registrar for your money back and file a complaint
with the FTC (www.ftc.gov).
FYI: Due to the problems that the duplication is causing, the operators of the original .BIZ will close it down
once all of the registrations in it expire (in several years). Your problem will then go away, because there will only be one
version of .BIZ. This will take us back to the stable state of affairs that occurred before ICANN broke the internet.
John Palmer
ADNS Customer Service.
----- Original Message -----
From: "Irate website operator" emailaddr@deleted.com
To: <info@adns.net>
Sent: Thursday, September 26, 2002 10:54
Subject: technical help needed asap!!
>
> Hello!
>
> I have a web site hosted by BellSouth.net - and registered as DOMAINNAMEDELETED.BIZ - which I beleive
your company has registered. As we try to access this site from any ISP other than BellSouth, we are getting an error
message that this domain name is not registered.A trace route of the problem showed that our "hops" are stopping at
AGN Domain Name Services, directly before the last stop at BellSouth.net. Apparently, there is an issue there we
need help with!! I've contacted our ISP, and they were able to tell me that the issue is outside of their network, and stops at
AGN.
>
> I originally registered this domain name with a 3 or 5 year term (registered about a year ago) - please ensure that I am still
active and call me to help resolve this issue ASAP!! Our business at DELETED is really on hold until our web site is back up
and running!! THANK YOU!!!
>
> Copy of trace route info:
etc . etc . etc.
--
This message was passed to you via the ga-full@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga-full" in the body of the message).
Archives at http://www.dnso.org/archives.html
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|