Jump to content

.arpa

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by InternetArchiveBot (talk | contribs) at 20:07, 21 August 2018 (Rescuing 1 sources and tagging 0 as dead. #IABot (v2.0beta8)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

arpa
IntroducedJanuary 1, 1985; 39 years ago (1985-01-01)
TLD typeInfrastructure domain
StatusActive
RegistryIANA
SponsorInternet Architecture Board
Intended useAddress and Routing Parameter Area: Internet infrastructure such as reverse IP lookup.
Registration restrictionsNo domain registrations possible, new subdomains rarely added
StructureSecond-level domains provide special name spaces for database functions
DocumentsRFC 3172
Dispute policiesNone
DNSSECyes
Registry websiteIANA .arpa info

The domain name arpa is a top-level domain (TLD) in the Domain Name System of the Internet. It is used exclusively for technical infrastructure purposes. While the name was originally the acronym for the Advanced Research Projects Agency (ARPA), the funding organization in the United States that developed one of the precursors of the Internet (ARPANET), it now stands for Address and Routing Parameter Area.

arpa also contains the domains for reverse domain name resolution in-addr.arpa and ip6.arpa for IPv4 and IPv6, respectively.

History

The arpa top-level domain was the first domain installed in the Domain Name System (DNS). It was originally intended to be a temporary domain to facilitate the transition of the ARPANET host naming conventions and the host table distribution methods to the Domain Name System. The ARPANET was one of the predecessors to the Internet, established by the United States Department of Defense Advanced Research Projects Agency (DARPA). When the Domain Name System was introduced in 1985, ARPANET host names were initially converted to domain names by adding the arpa domain name label to the end of the existing host name, separated with a full stop (i.e., a period). Domain names of this form were subsequently rapidly phased out by replacing them with domain names under the newly introduced, categorized top-level domains.

After arpa had served its transitional purpose, it proved impractical to remove the domain, because in-addr.arpa was used for reverse DNS lookup of IP addresses.[1] For example, the mapping of the IP address 192.0.2.155 to a host name is obtained by issuing a DNS query for a pointer record of the domain name 155.2.0.192.in-addr.arpa.

It was intended that new infrastructure databases would be created in the top-level domain int. However, in May 2000 this policy was reversed, and it was decided that arpa should be retained for this purpose, and int should be used solely by international organizations.[2] In accordance with this new policy, arpa now officially stands for Address and Routing Parameter Area (a backronym).[3]

Since March, 2010 the arpa zone is signed with DNSSEC.[4]

References

  1. ^ RFC 1035, Mockapetris, Paul (1987). "IN-ADDR.ARPA domain". Domain Names - Implementation and Specification. Internet Engineering Task Force. pp. 22 – 23. sec. 3.5. doi:10.17487/RFC1035. RFC 1035. Retrieved 2009-10-28. {{citation}}: Unknown parameter |month= ignored (help)
  2. ^ "IAB Statement on Infrastructure Domain and Subdomains". Archived from the original on 2009-05-11. Retrieved 2009-05-08. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  3. ^ RFC 3172, Huston, Geoff, ed. (2001). Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa"). Internet Engineering Task Force. p. 7. doi:10.17487/RFC3172. BCP 52. RFC 3172. Retrieved 2009-10-28. Further, as indicated by DARPA, the arpa TLD string should be given a different expansion such as "Address and Routing Parameter Area" to avoid any implication that DARPA has operational responsibility for the domain. {{citation}}: Unknown parameter |month= ignored (help)
  4. ^ https://web.archive.org/web/20100328000016/http://dnssec-deployment.org/pipermail/dnssec-deployment/2010-March/003730.html