Policy for Reverse Address Delegation under in-addr.arpa in the RIPE NCC Service Region Joao Luis Silva Damas Leo Vegoda Document ID: ripe-244 Date: 4 July 2002 _________________________________________________________________ Abstract This document describes the policy for reverse delegation of IPv4 assignments and allocations in the RIPE NCC service region. _________________________________________________________________ Contents 1.0 Introduction 2.0 Obtaining Delegation of an in-addr.arpa Sub-zone 3.0 Reverse Delegation for Provider Aggregatable (PA) Address Space 4.0 Reverse Delegation for Provider Independent (PI) Address Space 5.0 Duration of the Reverse Delegation 1.0 Introduction The RIPE NCC provides, as part of its services, the necessary support to enable the reverse resolution of IPv4 addresses into domain names. This service is implemented under the in-addr subdomain described in the "Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")"[RFC 3172] document. Delegations for IPv4 addresses contained in allocations made by the RIPE NCC (reverse delegations) are made by the RIPE NCC to the Local Internet Registries (LIRs) and further by the LIRs to Internet Service Providers or End Users. 2.0 Obtaining Delegation of an in-addr.arpa Sub-zone The RIPE NCC will only accept requests for reverse delegation under in-addr.arpa from LIRs. End Users must send their requests to the LIR from which they obtained the addresses, or in the case of Provider Independent addresses, to any of the LIRs of their choice. A list of LIRs can be found at: http://www.ripe.net/ripencc/mem-services/general/indices/index.html RIPE | Document Store | RIPE-244 Policy for Reverse Address Delega (p2 of 2) The procedure for requesting the delegation of zones under in-addr.arpa is published at: http://www.ripe.net/reverse/ Advice on configuring name servers is available in "Common DNS Operational and Configuration Errors" [RFC 1912] 3.0 Reverse Delegation for Provider Aggregatable (PA) Address Space The RIPE NCC accepts requests for reverse delegation solely for address space that has been allocated to an LIR and when at least one valid assignment has been registered to End Users in the RIPE Whois Database. The RIPE NCC will only make delegations on 8-bit boundaries (/16 or /24). Multiple delegations may be requested to cover CIDR blocks bigger than a /24. 4.0 Reverse Delegation for Provider Independent (PI) Address Space The RIPE NCC will reverse delegate a zone in in-addr.arpa to an End User that has been assigned PI space. However, the request must be sent to the RIPE NCC via an LIR as described above. For delegations of address blocks smaller than a /24 the method described in "Classless IN-ADDR.ARPA Delegation"[RFC 2317] will be used. 5.0 Duration of the Reverse Delegation Provision of reverse delegation services by the RIPE NCC is a membership service. As such, the RIPE NCC will only accept requests for delegation and modifications of delegations from LIRs that are up-to-date with regard to their membership duties. LIRs should provide reverse delegation corresponding to an assignment during the complete validity period of the assignment.