Hosting Multilingual Domain Names
It is quite simple to setup your DNS Manager to host a multilingual domain names. The procedure is similar to ASCII domain name hosting.
Before you begin, there are 2 conditions that you must meet. Check that:
- The domain name you intend to host must have been registered with i-DNS.net through its register partners.
- You have modified your DNS server such that it would be able to handle multilingual domain name queries. If you have not done so, please go to Enabling Multilingual Name Server
*Note: Multilingual Strings are converted into different ASCII compatible encodings(ACE) depending on the language.
The examples given in this guide use UTF5. Please use the correct ACE encoding based on the following table:
|Chinese(Simplified & Traditional)||UTF5|
|Tamil, Hindi, Telugu||UTF5|
Step 1: Preparation
- Convert your Multilingual Domain Name to UTF5
The legal range allowed in URLs is ASCII A-Z, 0-9 plus a ‘-’. Therefore, first convert the native string of your multilingual domain name to UTF5 format. UTF5 is a Unicode transformation format that transforms any given string into a ASCII string. (you may refer to Appendix 1 if you wish to understand the technical details on how UTF5 works.)
To convert native strings to UTF5, you can download ccode.exe (Windows program)
- Get ready the hostname of your Primary DNS server and IP address of your web server
The hostname is the one that was registered by you for your multilingual domain name during registration.
Step 2: Stop Windows NT DNS service
You can do that via "Start" -> "Setting" -> "Control Panel" ->
Select "Microsoft DNS Server" and click "stop" button.
Step 3: Start "DNS Manager"
Access "DNS Manager" via "Start" -> "Programs" ->
"Administrative Tools" -> "DNS Manager"
Step 4: Add a new server
Select "DNS" -> "New Server". Screen Shot
Enter the IP address of this server.
Step 5: Add a new zone
Select "DNS" -> "New Zone". Screen Shot
Select "Primary" and click "Next" Screen Shot
In "Zone Name", enter the UTF5 string of the multilingual domain name.
In "Zone File", enter a file name and click next.
If the NS record or SOA record is incorrect, edit them now.
To edit, right click at the record and select "Properties".
For both NS record and SOA record, change the "Primary name server DNS name" to the server name that you have registered as the primary name server in our database.
Step 6: Add a new record
Select "DNS" -> "New Record".Screen Shot
Select "A record".
Do not enter anything in the "Host Name" entry.
(Alternatively, you may enter the UTF5 string of your domain).
Enter the IP address of this primary server in the "Host IP Address" entry. Press "OK"
If the "DNS Manager" issues a warning, ignore it and just press "OK".
The above is the most basic setup for your multilingual domain. If you restart your DNS service now, it will be able to answer queries properly. In other words, in this example, if someone queries this name server for , your name server would return IP address "18.104.22.168".
If you wish to add a host in front of your domain,
first convert the host string to UTF5 and then add a
"A" record to your zone file :
For example, to add
a new record for "" and point it to IP address 22.214.171.124, first convert the host string "" to UTF5 string. The result is O04CL458.
Create a new "A" record.
Enter the UTF5 string "O04CL458" into "Host Name" and the IP address "126.96.36.199" into the "Host IP Address".
Therefore, when someone queries this DNS server for , it would return IP address
Step 7: Start the DNS Server.
What you’ve just done is to return an IP address whenever a client(application) queries this name server for the IP of your multilingual domain.
The client who made the query will now know which IP to send subsequent request to. Assuming that this IP is where your web server is running, the client (web browser) will send a http request to the web server asking for the webpage of your multilingual domain. Your web server will return a page from the web server’s default directory to the client.
The above procedures were tested with Windows NT SP3.
Back to top