The Internet Corporation for Assigned Names and Numbers (Icann) on Friday posted a notice on its Web site discussing its response to the so-called wildcard service, which launched on 15 September and sends users to a VeriSign page with search results including links to paid advertisements. VeriSign runs the registry for the .com and .net domains -- among the most widely used top level domains on the Web -- which are the domains affected by the wildcard service.
Icann said it is investigating complaints over the wildcard service and asked VeriSign to pull it pending further study. The service effectively replaces the common "404 page not found error" that until now has been the default for absent Web addresses.
"Recognising the concerns about the wildcard service, ICANN has called upon VeriSign to voluntarily suspend the service until the various reviews now under way are completed," the agency wrote in a notice posted on its Web site.
On Saturday, the Internet Architecture Board also weighed in on the controversy with an analysis of domain name system (DNS) wildcards. The group recommended that "DNS wildcards should not be used in a zone unless the zone operator has a clear understanding of the risks, and that they should not be used without the informed consent of those entities which have been delegated below the zone."
Criticism has been growing over VeriSign's surprise decision to take control of unassigned .com and .net domain names, which has confused antispam utilities and drawn angry denunciations of the company's business practices from frustrated network administrators.
VeriSign could not immediately be reached late on Sunday.
Last week, the company stood by its service.
"There is a lot of fiction about the actual technology and the service," VeriSign spokesman Brian O'Shaughnessy told CNET News.com earlier this week. "What we are doing is trying to determine fact and fiction and we're doing so by reaching out to the technology community and helping them to understand exactly what is fact and fiction."
VeriSign is not alone in seeking to replace 404 errors. Microsoft has also directed users of its Internet Explorer Web browser to a Microsoft search page when typing unassigned domain names into the browser's URL bar.
CNET News.com's Declan McCullagh contributed to this report.
Talkback
404 errors do not have anything to do with the DNS wildcard from verisign. 404 errors are returned on page not found events, not on domain not found. Domain not found does not have a http return code as if you can not found a DNS record for the page requested, there is no browser to web-server communication at all and therefore no room for return codes. Check your browser on http://www.zdnet.co.uk/Icannarticlehavesomemistakestobefixed.html