- Legend
- Added
- Deleted
Abstract
This document describes the policy for reverse delegation of IPv4 and IPv6 address space in the RIPE NCC service region.
Contents
1.0 2.0 Introduction Link: #introduction 3.0 Reverse Delegation in the RIPE NCC Service Region Link: #reverse_delegation 4.0 Procedures Link: #procedures 5.0 References Link: #references 6.0 Attribution Link: #attribution 1.1 Reverse delegation: The process by which the authority for certain reverse DNS zones is assigned to a specific set of DNS servers. 1.2 Early registration: IPv4 address space assigned or allocated before the establishment of the Regional Internet Registries (RIRs). Definition Link: #definition
1.0 Definition
2.0 Obtaining Delegation of an in-addr.arpa or ip6.arpa sub-domain Link: #delegation
3.0 Procedures Link: #procedures
4.0 References Link: #references 1.0
The RIPE NCC provides Link: #ref1 ] and [2] Link: #ref2 .provides, as part of its services, the necessary support to enable the reverse resolution of IPv4 and IPv6 address space into domain names. This service is implemented under the in-addr.arpa and ip6.arpa sub-domains described in [13.0 Reverse Delegation in the RIPE NCC Service Region
The RIPE NCC provides reverse Link: #references ] and [2 Link: #references ].Reverse
NCC.The RIPE NCC NCC are made to Local Internet Registries (LIRs) and further delegated by the LIRs to Internet Service Providers or End Users.
2.0 Obtaining Delegation of an in-addr.arpa or ip6.arpa sub-domain
Address space holders Registrants of address space allocations or assignments may delegate authority
to another party.
4.0The RIPE NCC accepts requests for reverse delegation for address space that has been allocated by the RIPE NCC to an LIR or, in the case of PI address space, an assignment that has been made to an End User.
The procedures related to for requesting and modifying reverse delegation and information about the requirements the RIPE NCC enforces to maintain the quality of the reverse delegations are published at:
http://www.ripe.net/reverse/ Link: http://www.ripe.net/reverse/ 5.0 References
[1] [RFC 3172 Link: ftp://ftp.ripe.net/rfc/rfc3172.txt ]
4.0 References
[2] [RFC 3596 Link: ftp://ftp.ripe.net/rfc/rfc3596.txt ] "DNS Extensions to Support IP Version 6", [RFC 3363 Link: ftp://ftp.ripe.net/rfc/rfc3363.txt ] “Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System”, [RFC 3364 Link: ftp://ftp.ripe.net/rfc/rfc3364.txt ] “Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version (IPv6)”
[RFC 3172 Link: ftp://ftp.ripe.net/rfc/rfc3172.txt ][2]
6.0 Attribution
This document is compiled from policies developed by the RIPE community.
The following people actively contributed to this policy by making proposals through the RIPE Policy Development Process:
Olaf Kolkman
Leo Vegoda