| Introduced | January 1, 1985; 41 years ago (1985-01-01) |
|---|---|
| TLD type | Infrastructure domain |
| Status | Active |
| Registry | IANA |
| Sponsor | Internet Architecture Board |
| Intended use | A temporary TLD to facilitate the transition fromARPANET to the DNS. |
| Actual use | Internet infrastructure such as reverse DNS lookup. |
| Registration restrictions | No domain registrations possible, new subdomains rarely added |
| Structure | Second-level domains used for various functions related to Internet infrastructure as defined by RFCs. |
| Documents | RFC 3172;RFC 9120 |
| Dispute policies | None |
| DNSSEC | Yes |
| Registry website | IANA .arpa info |
The domain namearpa is atop-level domain (TLD) in theDomain Name System (DNS) of theInternet. It is used predominantly for the management of technical network infrastructure. Prominent among such functions are the subdomainsin-addr.arpa andip6.arpa, which provide namespaces forreverse DNS lookup ofIPv4 andIPv6 addresses, respectively.
The name originally was theacronym for theAdvanced Research Projects Agency (ARPA), the funding organization in the United States that developed theARPANET, the precursor of the Internet. It was the first domain defined for the network in preparation for a hierarchical naming system for the delegation of authority, autonomy, and responsibility. It was originally intended only to serve in a temporary function for facilitating the systematic naming of the ARPANET computers. However, it became practically difficult to remove the domain after infrastructural uses had been sanctioned. As a result, the name was redefined as thebackronymAddress and Routing Parameter Area.
Domain-name registrations in arpa are not possible, and new subdomains are infrequently added by theInternet Engineering Task Force.
Each computer using theInternet Protocol is identified by a numericalIP address for identification and location addressing.[1] Each host is also assigned a more memorablehostname, which often relates to the purpose or ownership of the host, and is used more conveniently in user interaction with network functions, such as when connecting to or accessing a resource. Originally, the mapping between names and addresses was a cumbersome mechanical process using lookup tables distributed as computer files between network administrators. TheDomain Name System (DNS) solved this inefficiency by automating the lookup function with a hierarchical naming system using domain names. When a user requests a network service using a domain name, the protocol implementation (protocol stack) translates the name to an address that can be used to reach a remote host.
This naming function, often calledforward resolution, was the original purpose of the top-level domain "ARPA". It was the first domain defined in the first naming system of the nascent Internet,[2] and was supposed to be an initial container domain for all then-existing ARPANET hosts. The next stage of development of the naming architecture foresaw the establishment of specific domains for other purposes based on certain requirements.[2]
In many applications the reverse of the name-to-address mapping is also required. The host receiving a service request may require the domain name of the originating computer, for example, to customize the service, or for verification purposes. This latter function, calledReverse DNS lookup, is implemented in the major uses of the domainarpa: its subdomainsin-addr.arpa forInternet Protocol version 4, andip6.arpa forIPv6.
Conceptually similar lookup and mapping functionality is provided by other subdomains ofarpa for specific types of data.
The domain e164.arpa provides a lookup function that retrieves information associated withtelephone numbers through theENUM service. This service may be used to obtain the name of a computer that is capable of routing telecommunication requests for a registered telephone number, or obtain an email address to contact the subscriber of a specific telephone number.
The domain namehome.arpa was reserved by the Internet Engineering task force in May 2018 as aspecial-use domain name for non-unique DNS services in residential networking, to avoid the use of the top-level domainhome., which would require DNSSEC signatures.[3] In addition, the use ofhome. led to domain name leakage to the Internet root name servers. Theauthoritative name servers for home.arpa are the AS112blackhole servers,[4] which prevent leaked queries for home.arpa from burdening the root servers.[5]
TheARPANET, named for theAdvanced Research Projects Agency (ARPA), was launched in 1969, and is considered the earliest predecessor of theInternet. The agency's name was adopted as the name for the first formal name space of the network after it had transitioned toTCP/IP networking in January 1983.[2] The name was used as a naming suffix for all then-existing ARPANET hosts. Hierarchical domain-style names were intended to support delegation of responsibility and authority for adding future hosts to the network.
With the formal development of such a hierarchical naming system, the domain also became one of the inaugural members of a set of domain names for specific types of network members, namelycom for commercial users,org for organizations,edu for educational institutions,gov for government entities, andmil for networks of the United States military.[6]
It was expected that the use ofarpa would be temporary and that the existing systems would be migrated to other domains.[6] Butarpa also provided e-mail addresses associated with the Network Information Center, which administered the naming system. After serving the transitional purpose, it proved impractical to remove the domain. The domainin-addr.arpa had been installed forreverse DNS lookup of IP addresses.[7]: §3.5
Originally, the IETF intended that new infrastructure databases would be created in the top-level domainint. In May 2000, this policy was reversed and it was decided that the top-level domainint should be restricted to use by international organizations.[8]Arpa was retained for its long-standing purpose, but its full name was changed to theAddress and Routing Parameter Area, making the zone name abackronym.[9]: 7 Registrations of internet infrastructure services in.int made prior to this policy change, were optionally grandfathered in and not required to move to .arpa.
In March 2010, zone arpa was secured with digital signatures within theDomain Name System Security Extensions (DNSSEC).[10]
Subdomains ofarpa are created by resolution in the work groups of the Internet Engineering Task Force via theRequest for Comments process, and are maintained by theInternet Assigned Numbers Authority (IANA). The DNS zonearpa has the following subdomains:[11][12]
| Domain | Purpose | Authority document (RFC) |
|---|---|---|
| 6tisch.arpa | For IPv6 over theTime Slotted Channel Hopping mode ofIEEE 802.15.4 | RFC 9031[13] |
| as112.arpa | Sinking of DNS traffic for reverse IP address resolutions, misc. (seeBlackhole server) | RFC 7535[14] |
| e164.arpa | Mapping ofE.164 numbers to InternetURIs | RFC 6116[15] |
| eap-noob.arpa | For the Nimble Out-Of-Band authentication method of theExtensible Authentication Protocol framework | RFC 9140[16] |
| home.arpa | Residential networking | RFC 8375[3] |
| in-addr.arpa | Mapping ofIPv4 addresses to domain names | RFC 1035[7] |
| ip6.arpa | Mapping ofIPv6 addresses to domain names | RFC 3152[17] |
| in-addr-servers.arpa | Domains for authoritative DNS servers for the reverse lookup domains | RFC 5855[18] |
| ip6-servers.arpa | ||
| ipv4only.arpa | Detection of DNS64 availability and NAT64 prefix | RFC 7050[19] |
| iris.arpa | Locating Internet registry information services | RFC 4698[20] |
| ns.arpa | Domain for hosting authoritative DNS servers for the .arpa domain | RFC 9120[21] |
| resolver.arpa | Domain for discovery of designated DNS resolvers | RFC 9462[22] |
| service.arpa | For DNS-based service discovery over unicast | RFC 9665[23] |
| uri.arpa | Resolution of URIs andURNs, according to theDynamic Delegation Discovery System | RFC 3405[24] |
| urn.arpa |
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.
(987)