AfriNIC Policy for reverse delegation on Allocated IP addresses


  • Ref. Name:
  • Old Ref:
  • Status:
  • Date:
    30 Jun 2004
  • Author:
    • Adiel Akplogan
    • Ernest Byaruhanga

1) Abstract

This document describes the policy for reverse delegation of IPv4 assignments and allocations in the AFRINIC service region. Please note that AFRINIC registers only reverse delegations and is not involved in the domain name registration system.


2) Introduction

AFRINIC provides support to enable applications to map to a domain name from an IP address. Reverse delegation is achieved by use of the (IPv4) and (IPv6) domains.


3) Obtaining Delegation of an Sub-zone

AFRINIC only accepts requests for reverse delegation under from AFRINIC active 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. AFRINIC will carry out tests to ensure that the name server for the zone that the reverse delegation is being requested is up and configured as per the recommendedations in RFC1912.


4) Reverse Delegation for Provider Aggregatable (PA) Address Space

AFRINIC will only make delegations on 8-bit boundaries (/16 or /24). Multiple delegations may be requested to cover CIDR prefixes shorter blocks bigger than a /24.


5) Reverse Delegation for Provider Independent (PI) Address Space

AFRINIC will reverse delegate a zone in to an End User that has been assigned PI space.

For delegations of address blocks smaller than a /24 the method described in "Classless IN-ADDR.ARPA Delegation"[RFC 2317] will be used.


6) Validity of the Reverse Delegation

AFRINIC accepts requests for delegation and modifications of delegations from LIRs whose membership status is up-to-date.

Ipv6 Reverse Delegation

IETF consensus was reached that the IP6.ARPA domain be used for address to DNS name mapping for the IPv6 address space. Refer to: