Talk:.arpa

Misc
Address and Routing Parameter Area (a "backronym")  ????? --206.248.134.103


 * What exactly is the problem? In the article, the word backronym is linked, so you can click to see what it means. --Zundark 08:26, 21 April 2006 (UTC)


 * Actually... it's a retronym, as the link now indicates. 131.243.47.233 (talk) 17:28, 21 February 2020 (UTC)

http://16.16-28.45.70.166.in-addr.arpa/
How did someone do this? 62.66.194.63 19:46, 8 June 2006 (UTC)


 * He got delegated the 16-28.45.70.166.in-addr.arpa. zone from his provider and simply added an A record to the 16.16-28.... entry pointing to 166.70.45.21. And that's where a webserver's running which evaluates the hostname and returns the "isn't it cool"-page if you're asking the in-addr.arpa. URL. Sigkill 20:07, 10 June 2006 (UTC)

Article misnamed
This article is misnamed. Pedantically speaking the zone is not called ".arpa" but rather "arpa" (fully qualified: "arpa."). See RFC3172. That said, many people refer to it by the degenerative ".zone" form of ".arpa", including the IANA website. (Paul Jakma). —Preceding unsigned comment added by 81.168.24.37 (talk) 08:41, 15 August 2008 (UTC)

While you are technically and normatively correct, it's typical that TLDs are written in the form ".example", although the domain itself is either "example" or absolutely "example.". --Cálestyo (talk) 01:26, 25 December 2010 (UTC)

in-addr.arpa server operation
Who is operating servers that participate in in-addr.arpa reverse lookup? Is it mandatory for an IP owner to allow reverse DNS lookup using in-addr.arpa? --Abdull (talk) 16:38, 10 July 2012 (UTC)

Rewrite of article
The article has been rewritten essentially in its entirety to reflect current intent and usage of the domain and all subdomains. An editor insists to reorder the sections to emphasize history over actual current purpose. In technology articles, WP often, perhaps mostly, first defines the subject matter before reciting its history. Most readers most likely are looking for definition before history. Kbrose (talk) 15:05, 18 June 2020 (UTC)

Structure parameter of infobox
I edited the structure parameter of the infobox as the previous value was just about the second-level domains that map some other identifier to a domain, such as in-addr.arpa, ip6.arpa, e164.arpa, uri.arpa, and urn.arpa.

Many of the newer domains have other purposes, such as trying to detect presence of DNS64, non-unique use in home networks, etc.

A better option might be to remove the structure parameter as there is really no structure that applies to all of them, other than each function having a specific second-level domain. Meowthia (talk) 22:32, 29 June 2022 (UTC)