Frequently Asked Questions (FAQ) |
We are not all Americans, it requires effort by everybody to understand and adapt to a multi-cultural environment.
Complaints against ICANN Accredited Registrars
Root servers.
The list of 13 current root servers
The map of 13 current root servers
- http://www.wia.org/pub/rootserv.html
The WIA map (February 1998) is partly outdated.
The official ICANN documents include the correct one, for example: http://www.icann.org/correspondence/roberts-testimony-14feb01.htm (Testimony of Michael M. Roberts Before U.S. Senate Committee on Commerce, Science, and Transportation, Subcommittee on Communications).
There is no much difference in geography between the two constellations (www.wia.org and Mike Roberts document), only names are updated (no more reference to NSI-NSF etc).
According to Mike Roberts document:
ROOT-SERVERS name org city type a NSI Herndon, VA, US com b USC-ISI Marina del Rey, CA, US edu c PSInet Herndon, VA, US com d U of Maryland College Park, MD, US edu e NASA Mt View, CA, US usg f Internet Software C. Palo Alto, CA, US com g DISA Vienna, VA, US usg h ARL Aberdeen, MD, US usg i NORDUnet Stockholm, SE int j NSI (TBD) Herndon, VA, US (com) k RIPE London, UK int l ICANN Marina del Rey, CA, US org m WIDE Tokyo, JP edu
IAB Technical Comment on the Unique DNS Root
Domain names registration.
Generic TLDs - gTLDs, each with its charter for registration
- To register a domain name in the .aero, .biz, .com, .coop, .info, .museum, .name, .net, .org, .pro domains, please contact one of the ICANN Accredited Registrars: http://www.icann.org/registrars/accredited-list.html
Restricted generic TLDs - gTLDs
The .gov domain http://www.nic.gov is reserved exclusively for the United States Government.
The .mil domain http://www.nic.mil is reserved exclusively for the United States Military.
The .edu domain http://www.nsi.com is registered only through Network Solutions.
The .int domain http://www.iana.org/int.html is used only for registering organizations established by international treaties between governments or Internet infrastructure databases (for example to do address to name lookups based on NSAPs). If you believe you meet these qualifications and want to apply for a domain name under .int, please send the IANA a description of your organization including a reference to the treaty that established it or click http://www.iana.org/int-reg.html for the online application. Please note that the online application must be supplemented with a reference to the treaty which established it.
Country code TLDs - ccTLDs
To register a domain name in a country code TLD (such as .br, .ca, .cn, .de, .fr, .jp, .mg, .mx, uk, ... ), please contact the corresponding ccTLD registry: http://www.iana.org/cctld/cctld.htm.
The list of ccTLD's Nic-handles is helpful for the whois queries http://www.dnso.org/dnso/ccTLDs-handles.html.
See also the list of URLs for ccTLD Registries around the world mainained by the Norwegian Registry http://www.uninett.no/navn/domreg.html
The list of States party to the Paris Convention for the Protection of Industrial Property is maintained at http://www.wipo.org/eng/ratific/d-paris.htm.
The United Nations Statistics Division provides information on Standard Country or Area Codes and Geographical Regions for Statistical Use http://www.un.org/Depts/unsd/methods/m49.htm
The ccTLDs are based on the ISO3166 code. For more information see the ISO 3166 Maintenance Agency website http://www.din.de/gremien/nas/nabd/iso3166ma/.
Excerpt from "How to get a country name into ISO 3166-1" http://www.din.de/gremien/nas/nabd/iso3166ma/get_name.html:
III. A request for the inclusion of a country name (or the name of a dependent area) in ISO 3166-1 must originate from the national government of the country or from the national standards body of that country. The ISO 3166/MA rejects any request which is not accompanied by a written statement from the national goverment explicitly agreeing to and supporting the request.Since 2000 ICANN/IANA had to state on Delegation/Redelagation/Deletion for ccTLDs:
- 11 Feb 2000, IANA Report on Request for Redelegation of the .pn Top-Level Domain http://www.icann.org/general/pn-report-11feb00.htm
- 22 Mar 2000, IANA Report on Request for Delegation of the .ps Top-Level Domain http://www.icann.org/general/ps-report-22mar00.htm
- 01 Dec 2000, IANA Report on Request for Redelegation of the .ca Top-Level Domain http://www.iana.org/reports/ca-report-01dec00.htm
- 20 Jun 2001, IANA Report on Deletion of the .zr Top-Level Domain http://www.iana.org/reports/zr-report-20jun01.htm
- 31 Aug 2001, IANA Report on Request for Redelegation of the .au Top-Level Domain http://www.iana.org/reports/au-report-31aug01.htm
- 19 Nov 2001, Second IANA Report on Request for Redelegation of the .au Top-Level Domain http://www.iana.org/reports/au-report-19nov01.htm
- 19 Nov 2001, ICANN Announcement on Redelegation of the .us Top-Level Domain http://www.icann.org/announcements/announcement-19nov01.htm . This redelegation occurred before the completion of the normal IANA requirements.
- 08 Feb 2002, IANA Report on Request for Redelegation of the .jp Top-Level Domain http://www.iana.org/reports/jp-report-08feb02.htm .
NOTE, Oct 2001
We note that IANA publishes now list of IANA reports since 2000 in http://www.iana.org/domain-names.htmPlease note that ccTLD's policies vary. The list of URLs above is intended to help you to find the following information:
- in which country a ccTLD registry is located
- in which country a ccTLD registry is incorporated (if private company)
- under which country law a ccTLD registry operates
- charter of a ccTLD registry
- liability of a ccTLD registry
- technical capability of a ccTLD registry
The General Assembly main mailing list - ga@dnso.org - rules are:
- --Limit comments to those related to the topic of the DNSO
- --Consider this list precious, and take care of it.
- --Consider time necessary to read all comments, especially for non native English speakers.
- --Respect other participants, do not insult anybody.
- --Do not cross-post messages.
- --Do not post advertisements.
Information from: |
© ICANN/DNSO |