监管落地期限临近 关停并转风起80%网贷平台将出局
百度 对于鹿泉而言，打造全域旅游示范区，生态是基础、绿化是保障。A name collision occurs when an attempt to resolve a name used in a private name space (e.g. under a non-delegated Top-Level Domain, or a short, unqualified name) results in a query to the public Domain Name System (DNS). When the administrative boundaries of private and public namespaces overlap, name resolution may yield unintended or harmful results.
Name collisions are not new. The introduction of any new Domain Name into the DNS, whether a generic TLD, country code TLD or Second-Level Domain name (SLD) creates the potential for name collision. A secure, stable and resilient Internet is ICANN's number one priority. Therefore, we've made a commitment to the Internet community to launch a substantial effort to mitigate and manage collision occurrence.
If your system is suffering demonstrably severe harm as a consequence of name collision, please fill in the form below to report the incident.
ICANN will initiate an emergency response for name collision reports only where there is a reasonable belief that the name collision presents a clear and present danger to human life.
The emergency response could include temporarily removing the effected SLD or the entire TLD from the DNS. ICANN will serve as the initial reporting point, and if necessary will coordinate with registry operators to ensure that the report is acted upon in an expedited manner. ICANN's contracted Registry Operators are required to act on requests from ICANN within 2 hours of receipt of the request from ICANN.
If you believe your name collision meets the criteria above (i.e. your system is suffering demonstrably severe harm as a consequence of name collision or you have a reasonable belief that the name collision presents a clear and present danger to human life), please use the form below to submit your report to ICANN.
After submitting the report, please review the Guide to Name Collision Identification and Mitigation for IT Professionals [PDF, 476 KB] for more information.
All fields marked with asterisk ("*") are required.