ARPA DNS Zone

From IAB Wiki
Revision as of 17:31, 11 June 2020 by Whardaker (talk | contribs) (Created page with "== Background == The IAB is responsible for the contents of the .arpa DNS TLD. == Approving ARPA change requests == Changes to the .arpa zone will be received by IANA and t...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Background

The IAB is responsible for the contents of the .arpa DNS TLD.

Approving ARPA change requests

Changes to the .arpa zone will be received by IANA and the IAB will be notified to approve of changes. An IAB member will be selected each year to handle approval requests from IANA. The responsible IAB member will need to approve or handle the request in coordination with the larger IAB. For some, it is trivial (updated IP addresses, etc.) and the approver can just say yes. If the approver doesn't think it is trivial, it would go to the full IAB for discussion or a vote.

Guidance for authors writing IANA considerations sections

[from Michelle]:

Draft-ietf-homenet-dot-14.txt was recently approved for publication as an RFC (see announcement below). As this document requests the addition of the special name “home” added to the .arpa zone, we are requesting approval from the IAB (per RFC 3172) in order to complete these actions. Please provide a response as soon as possible.


Once approved, the IAB will receive a request for confirmation from IANA Root Zone Management to confirm the specifics related to home.arpa request.

Other notes

- Some entries may go directly into .arpa - Others will create sub-domains (eg in-addr-servers.arpa.) - Others will be subdomains that deliberately blackhole requests (eg home.arpa) - .arpa is a DNSSEC signed zones, and subzones should be encouraged to sign as well (placing a DS record in the .arpa zone pointing to the sub-zones keys)