.arpa
| Introduced | January 1, 1985 |
|---|---|
| TLD type | Infrastructure domain |
| Status | Active |
| Registry | IANA |
| Sponsor | Internet Architecture Board |
| Intended use | A temporary TLD to facilitate the transition from ARPANET 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 name arpa is a top-level domain (TLD) in the Domain Name System (DNS) of the Internet. It is used predominantly for the management of technical network infrastructure. Prominent among such functions are the subdomains in-addr.arpa and ip6.arpa, which provide namespaces for reverse DNS lookup of IPv4 and IPv6 addresses, respectively.
The name originally was the acronym for the Advanced Research Projects Agency (ARPA), the funding organization in the United States that developed the ARPANET, 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 the backronym Address and Routing Parameter Area.
Domain-name registrations in arpa are not possible, and new subdomains are infrequently added by the Internet Engineering Task Force.
Purpose
Each computer using the Internet Protocol is identified by a numerical IP address for identification and location addressing.[1] Each host is also assigned a more memorable hostname, 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. The Domain 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 called forward 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]
Reverse IP address mapping
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, called Reverse DNS lookup, is implemented in the major uses of the domain arpa: its subdomains in-addr.arpa for Internet Protocol version 4, and ip6.arpa for IPv6.
Conceptually similar lookup and mapping functionality is provided by other subdomains of arpa for specific types of data.
Telephone number mapping
The domain e164.arpa provides a lookup function that retrieves information associated with telephone numbers through the ENUM 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.
Residential networking
The domain name home.arpa was reserved by the Internet Engineering task force in May 2018 as a special-use domain name for non-unique DNS services in residential networking, to avoid the use of the top-level domain home., which would require DNSSEC signatures.[3] In addition, the use of home. led to domain name leakage to the Internet root name servers. The authoritative name servers for home.arpa intercept locally unresolved queries for the domain and return addresses for certain blackhole servers.
History
The ARPANET, named for the Advanced Research Projects Agency (ARPA), was launched in 1969, and is considered the earliest predecessor of the Internet. The agency's name was adopted as the name for the first formal name space of the network after it had transitioned to TCP/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, namely com for commercial users, org for organizations, edu for educational institutions, gov for government entities, and mil for networks of the United States military.[4]
It was expected that the use of arpa would be temporary and that the existing systems would be migrated to other domains.[4] But arpa 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 domain in-addr.arpa had been installed for reverse DNS lookup of IP addresses.[5]
Originally, the IETF intended that new infrastructure databases would be created in the top-level domain int. In May 2000, this policy was reversed and it was decided that the top-level domain int should be restricted to use by international organizations.[6] Arpa was retained for its long-standing purpose, but its full name was changed to the Address and Routing Parameter Area, making the zone name a backronym.[7]
In March 2010, zone arpa was secured with digital signatures within the Domain Name System Security Extensions (DNSSEC).[8]
Subdomains
Subdomains of arpa are created by resolution in the work groups of the Internet Engineering Task Force via the Request for Comments process, and are maintained by the Internet Assigned Numbers Authority (IANA). The DNS zone arpa has the following subdomains:[9][10]
| Domain | Purpose | Authority document |
|---|---|---|
| 6tisch.arpa | For IPv6 over the Time Slotted Channel Hopping mode of IEEE 802.15.4 | RFC 9031 |
| as112.arpa | Sinking of DNS traffic for reverse IP address resolutions, misc. | RFC 7535 |
| e164.arpa | Mapping of E.164 numbers to Internet URIs | RFC 6116 |
| eap-noob.arpa | For the Nimble Out-Of-Band authentication method of the Extensible Authentication Protocol framework | RFC 9140 |
| home.arpa | Residential networking | RFC 8375 |
| in-addr.arpa | Mapping of IPv4 addresses to domain names | RFC 1035 |
| ip6.arpa | Mapping of IPv6 addresses to domain names | RFC 3152 |
| in-addr-servers.arpa | Domains for authoritative DNS servers for the reverse lookup domains | RFC 5855 |
| ip6-servers.arpa | ||
| ipv4only.arpa | Detection of DNS64 availability and NAT64 prefix | RFC 7050 |
| iris.arpa | Locating Internet registry information services | RFC 4698 |
| ns.arpa | Domain for hosting authoritative DNS servers for the .arpa domain | RFC 9120 |
| resolver.arpa | Domain for discovery of designated DNS resolvers | Internet Draft draft-ietf-add-ddr-10 |
| uri.arpa | Resolution of URIs and URNs, according to the Dynamic Delegation Discovery System |
RFC 3405 |
| urn.arpa |
References
- ^ J. Postel, ed. (September 1981). Internet Protocol, DARPA Internet Program Protocol Specification. IETF. doi:10.17487/RFC0791. RFC 791.
- ^ a b c RFC 881, The Domain Name Plan and Schedule, J. Postel, IETF (November 1983)
- ^ RFC 8375, Special-Use Domain home.arpa, P. Pfister, T. Lemon, IETF (May 2018)
- ^ a b RFC 920, J. Postel, J. Reynolds, Domain Requirements, IETF (October 1984)
- ^ Mockapetris, Paul (November 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 October 28, 2009.
- ^ "IAB Statement on Infrastructure Domain and Subdomains". Archived from the original on 27 August 2003. Retrieved 1 August 2019.
- ^ Huston, Geoff, ed. (September 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 October 28, 2009.
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.
- ^ "[Dnssec-deployment] Signing of the ARPA zone". Archived from the original on March 28, 2010.
- ^ ".arpa". ICANN. Archived from the original on January 7, 2009. Retrieved June 17, 2020.
- ^ ".ARPA Zone Management". Internet Assigned Numbers Authority (IANA). Retrieved March 2, 2023.