How to Resolve Arabic Domain Names
(Version 0.2)
Date: 27 April 2005
Prepared by: GCC-ADNS Taskforce
1. Introduction
Since ICANN has not yet supported full
Arabic ccTLD any solution for supporting Arabic domain names would
be only accessible locally. Therefore, there should be a hacking
solution until Arabic domain names is world-wide supported. Hence,
any entity needs to reach GCC Arabic domain names must therefore do
some changes in the configuration files of their resolving/caching
name servers..
2. Hacking solution for enabling Arabic domains
on your Resolver
The Task force has agreed on using the
“stub zone” configuration option for any entity that needs to
resolve GCC Arabic domain names. A “stub” zone is like a “slave”
zone, except that it replicates only the NS records of a master zone
instead of the entire zone.
Therefore, if any entity wants to
resolve Arabic GCC ccTLD domain names they should configure all the
Arabic GCC ccTLD as “stub” zones in the configuration of their name
server and point them to the GCC Arabic root servers.
3. Configuring Bind name server
Here is an example on how to configure
stub zone using bind version 8 or higher in the file “named.conf”
for all the GCC Arabic ccTLDs:
// e.g. : add these lines to your named.conf file.
// contact GCC-ADNS Taskforce to get the updated list
zone “xn--mgberp4a5d4ar” {
type stub;
file “sa.idn.zone” ;
masters { 213.42.20.76; 212.26.18.12; };
};
zone “xn--kgbdbap4b0ij” {
type stub;
file “ae.idn.zone” ;
masters { 213.42.20.76; 212.26.18.12; };
};
File: named.conf
But our recommendation is to use the "include" statement instead
of defining them directly in your "named.conf", as follows:
// e.g. : add these lines to your named.conf file.
// contact GCC-ADNS Taskforce to get the updated list
Include "Arabic_ccTLD_stub_zone_files.inc";
File: named.conf
Please contact the GCC-ADNS Taskforce to get the up-to-date list)
of all stub zones (Arabic_ccTLD_stub_zone_files.inc.
More information
|
