.af: Difference between revisions
No edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
The .af ccTLD was one of the first ones to be re-delegated in the Middle East region. It was re-delegated by the [[IANA]] in October 1997, wherein [[NetNames]] agreed to perform technical operations and provide free registration services on a temporary basis, until a stable registry operation could be established within the country. However, due to the country's ungoing civil war in the late '90s, NetNames, in consultation with IANA, halted registration of .af domain names, though it continued to make nameserver updates and to provide DNS resolution for the zone. By early 2000, NetNames and IANA could no longer have an on-site administrative contact person, as the one they did havea disappeared.<ref name="study"></ref> | The .af ccTLD was one of the first ones to be re-delegated in the Middle East region. It was re-delegated by the [[IANA]] in October 1997, wherein [[NetNames]] agreed to perform technical operations and provide free registration services on a temporary basis, until a stable registry operation could be established within the country. However, due to the country's ungoing civil war in the late '90s, NetNames, in consultation with IANA, halted registration of .af domain names, though it continued to make nameserver updates and to provide DNS resolution for the zone. By early 2000, NetNames and IANA could no longer have an on-site administrative contact person, as the one they did havea disappeared.<ref name="study"></ref> | ||
It was under approval of the [[Afghan Interim | It was under approval of the [[Afghan Interim Administration]] that the [[UNDP]] assumed the administration of the [[.af]] registry. Only a very small internet community was found in Afghanistan at that time, primarily established by international organizations and NGOs located in Kabul. The UNDP agreed that, whenever possible, it would restore DNS service, build technical and administrative capacity within Afghanistan, and to shift technical operations to a community-based structure that included many sectors of society.<ref name="study"></ref> | ||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
Revision as of 20:11, 24 November 2015
| Status: | Active |
| country: | Afghanistan |
| Registry Provider: | Ministry of Communications and IT |
| Type: | ccTLD |
More information: 
| |
.af is the Country Code Top-Level Domain (ccTLD) for Afghnistan.[1]
Its national domain administrator and registry operator are both governmental organisations. Afghanistan Network Information Centre (AFGNIC) is the operator and a department under the TLD Administrator, ICT Directorate, Ministry of Communications and Information Technology, is the domain administrator.[2]
The .af ccTLD was one of the first ones to be re-delegated in the Middle East region. It was re-delegated by the IANA in October 1997, wherein NetNames agreed to perform technical operations and provide free registration services on a temporary basis, until a stable registry operation could be established within the country. However, due to the country's ungoing civil war in the late '90s, NetNames, in consultation with IANA, halted registration of .af domain names, though it continued to make nameserver updates and to provide DNS resolution for the zone. By early 2000, NetNames and IANA could no longer have an on-site administrative contact person, as the one they did havea disappeared.[2]
It was under approval of the Afghan Interim Administration that the UNDP assumed the administration of the .af registry. Only a very small internet community was found in Afghanistan at that time, primarily established by international organizations and NGOs located in Kabul. The UNDP agreed that, whenever possible, it would restore DNS service, build technical and administrative capacity within Afghanistan, and to shift technical operations to a community-based structure that included many sectors of society.[2]
References[edit | edit source]
- ↑ Delegation Record for .AF, IANA.org. Retrieved 2015 July 6.
- ↑ 2.0 2.1 2.2 MEAC DNS Study, ICANN.org. Published 2015 October 13. Retrieved 2015 November 12.