Skip to main content
Resources

为新 ccTLD 缓和域名冲突事件

本页面还提供其他语种：

域名冲突 | 向 IT 人士发布的域名冲突识别和缓和措施指南 | 常见问题与解答：向 IT 人士发布的域名冲突识别和缓和措施指南 | 为新 ccTLD 缓和域名冲突事件 | 常见问题与解答：面向注册管理机构的域名冲突事件管理框架 | 报告域名冲突

ICANN 的使命与核心价值要求 ICANN 维护并加强互联网唯一标识符系统（域名、IP 地址和协议参数）的运营稳定性、可靠性、安全性以及全球互用性1。为践行使命与核心价值、遵循董事会的指示，以及考虑安全与稳定咨询委员会提出的建议，ICANN 始终致力于理解并缓和与域名系统 (Domain Name System, DNS) 中的"域名冲突"相关的问题。

域名冲突是指这样一种情况：原本应在一个域名系统中解析的资源名称，却意外地在另一个域名系统中解析，这可能导致意外行为，例如通信中断或者重定向到非预期的收件人。

根据 ICANN 的"新通用顶级域 (generic Top-level Domain, gTLD) 冲突事件管理"规划 <https://www.icann.org/en/system/files/files/resolutions-new-gtld-annex-1-07oct13-en.pdf> [PDF, 840 KB] 和"域名冲突事件管理框架"<https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf> [PDF, 635 KB]，ICANN 已要求 2012 轮次的新 gTLD 运营商实施特定措施，以帮助缓和域名冲突风险。

域名冲突的风险并非新 gTLD 所独有，也可能出现在 ASCII 及 IDN 形式的新国家和地区顶级域 (country code Top Level Domain, ccTLD) 中。为帮助缓和未来新的 ccTLD 中的域名冲突风险，ICANN 强烈建议采取以下措施：

新 ccTLD 经理人应至少在 90 天内实施持续的"控制性中断"，将以下记录插入 ccTLD 区（将"TLD"替换为您的新 ccTLD 字符串）：

TLD. 3600 IN MX 10 your-dns-needs-immediate-attention.TLD.
*    3600 IN MX 10 your-dns-needs-immediate-attention.TLD.
TLD.3600 IN SRV 10 10 0 your-dns-needs-immediate-attention.TLD.
*    3600 IN SRV 10 10 0 your-dns-needs-immediate-attention.TLD.
TLD.3600 IN A 127.0.53.53
*           3600 IN A 127.0.53.53
TLD. 3600 IN TXT "Your DNS configuration needs immediate attention see https://icann.org/namecollision"
*    3600 IN TXT "Your DNS configuration needs immediate attention see https://icann.org/namecollision"

根据 SAC0152 中的讨论，ICANN 建议，针对用于为第三方提供注册的域名，不要在 DNS 中使用通配符记录。因此，在 90 天的控制性中断期结束之前，不得在该顶级域 (TLD) 下注册任何域名，或者至少不应激活任何域名。要了解有关使用通配符记录的更多信息，请参阅 <https://archive.icann.org/en/topics/new-gtlds/nxdomain-substitution-harms-24nov09-en.pdf> [PDF, 227 KB]

建议新 ccTLD 经理人至少在新 ccTLD 运营初期实施域名冲突报告机制，以便对域名冲突引发的严重危害情况采取应对措施（有关示例，请参阅 <https://forms.icann.org/en/help/name-collision/report-problems>）。可采取措施的示例包括：在控制性中断期内从 DNS 中移除通配符记录；从 DNS 中移除二级域名；以及在极端情况下，从根区中移除该顶级域本身（例如，在控制性中断期内，因顶级域自身，即无点域名，造成危害的情形）。请注意，这些措施都只是临时性安排，可以让受影响的相关方有时间调整其网络配置，以避免后续危害。

ICANN 秉持自己的使命与核心价值，全身心投入为新 gTLD 授权的工作之中。ICANN 感谢您对此问题的关注，并随时准备在需要时开展进一步合作。

1 https://www.icann.org/resources/pages/bylaws-2012-02-25-en，第 1 条

2 https://www.icann.org/resources/pages/sac-015-2012-02-25-en

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."