 |
Internationalized Domain Names |
|
|
IDN FAQs - Procedures
How will internationalized
domain names be processed?
The registrar will use Punycode and valid name
prep checks to convert native language characters into ASCII-compliant
codes. These ASCII strings will then be sent to the VeriSign database.
Back to top
What is the encoding used for
this process?
Based on the IETF published RFC 3492 (Request
for Comment), the encoding will be Punycode.
Back to top
May hyphens be used in internationalized
domain names?
Yes. Hyphens may be used in internationalized
domain names. However, just as current standards do not allow names
to begin or end with a hyphen, the ASCII transformation cannot begin
or end with a hyphen.
Back to top
What is the maximum number
of characters allowed for an internationalized domain name?
The encoded form of the internationalized domain
name (including the 4 characters for .com or .net) may contain up to
67 characters. The characters can be letters, numbers, and/or hyphens.
Hyphens may not begin or end a domain name. The internationalized domain
name transformation software will reject the name if the encoded conversion
exceeds the limit.
Back to top
What is the format of the domain
name when it is entered into the VeriSign database?
Internationalized domain names are stored in
the VeriSign database as ASCII-compliant punycode codes with .com or
.net suffixes.
Back to top
How will internationalized
domain names appear in the Zone file, as the actual name in the native
character set, or as the ASCII transformation?
When in the Zone file, internationalized domain
names will appear as the encoded ASCII character string. For example,
the punycode encoding of domain.com will be stored as xn--eckwd4c7c.com.
Back to top
Will there be separate EPP
codes to indicate registration failures/errors for internationalized
domain names and name servers?
The registration failure/error codes for internationalized
domain names and name servers are the same as those in the current EPP.
Additional codes have been added to support errors specific to internationalized
domain name conversion and encoding.
Back to top
Failed to load XML file with Content ID '001387'.
|
Worldwide Sites
