You are here: Home > Publications > RIPE Document Store > Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain

Changes to Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-085: Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domai ripe-581: This document describes the policy for reverse delegation of IPv4 and IPv6 address space in the RIPE NCC service region.

delete:  Introduction delete:   delete:   insert: 

This document describes the procedures policy for the reverse delegation of au- delete:   thority of zones in the 193.in-addr.arpa domain. As of March delete:   16th 1993 the RIPE NCC has been delegated IPv4 and IPv6 address space in the RIPE NCC service region. insert: 

insert: <h3>

Contents insert: `</h3>`

insert: 

insert: <a class="anchor-link" href="#definition"> 1.0 Definition insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#introduction"> 2.0 Introduction insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#reverse_delegation"> 3.0 Reverse Delegation in the RIPE NCC Service Region insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#procedures"> 4.0 Procedures insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#references"> 5.0 References insert: </a> insert: 

insert: 

insert: <a class="anchor-link" href="#attribution"> 6.0 Attribution insert: </a> insert: 

insert: <h3>

insert: `<a name="definition">` insert: `</a>` 1.0 Definition insert: `</h3>`

insert: 

insert:  1.1 insert:  insert:  Reverse delegation: insert:  The process by which the authority for the delete:   193.in-addr.arpa domain from the root. Due to the fact that in delete:   the 193.x.y certain reverse DNS zones is assigned to a specific set of DNS servers. insert: 

insert: 

insert:  1.2 Early registration: insert:  IPv4 address space blocks assigned or allocated before the establishment of 256 class C network numbers delete:   are further delegated to local registries , the possibility ex- delete:   ists to the Regional Internet Registries (RIRs). insert: 

insert: 

insert: 

insert: 

insert: 

insert: <h3>

insert: `<a name="introduction">` insert: `</a>` 2.0 Introduction insert: `</h3>`

insert: 

The RIPE NCC provides the necessary support to enable 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 [ insert: <a class="anchor-link" href="#ref1"> 1 insert: </a> ] and [ insert: <a class="anchor-link" href="#ref2"> 2] insert: </a> . insert: 

insert: <h3>

insert: `<a name="reverse_delegation">` insert: `</a>` 3.0 Reverse Delegation in the RIPE NCC Service Region insert: `</h3>`

insert: 

The RIPE NCC provides reverse delegations for IPv4 and IPv6 address space that is registered by the RIPE NCC. insert: 

insert: 

The RIPE NCC also delegate the zone for these blocks in the 193.in- delete:   addr.arpa domain. This document describes some guidelines and delete:   procedures for this type of delegation and the provides systems to control reverse delegation of re- delete:   verse zones early registrations that have been transferred to the RIPE Database. insert: 

insert: 

Address space holders may delegate authority to another party. insert: 

insert: 

insert: 

insert: 

insert: 

insert: <h3>

insert: `<a name="procedures">` insert: `</a>` 4.0 Procedures insert: `</h3>`

insert: 

The procedures related to reverse delegation and information about the requirements the RIPE NCC enforces are published at: insert: 

insert: 

insert: <a href="http://www.ripe.net/reverse/"> http://www.ripe.net/reverse/ insert: </a> insert: 

insert: <h3>

insert: `<a name="references">` insert: `</a>` 5.0 References insert: `</h3>`

insert: 

insert: <a name="ref1"> insert: </a> [1] [ insert: <a class="external-link" href="ftp://ftp.ripe.net/rfc/rfc3172.txt"> RFC 3172 insert: </a> ] "Management Guidelines & Operational Requirements for individual class C networks in 193.x.y. delete:   delete:   delete:   A bit more explained delete:   delete:   With the assignment of class C network numbers following the CIDR delete:   (RFC 1338) model, in which large chunks of the address space are delete:   delegated to one region, and within that region blocks of class C delete:   network numbers are delegated to service providers and non- delete:   provider registries, some hierarchy in the address space is delete:   created, similar to the hierarchy in the domain name space. Due delete:   to this hierarchy the reverse the Address and Routing Parameter Area Domain ("arpa")" insert: 

insert: 

insert: <a name="ref2"> insert: </a> [2] [ insert: <a class="external-link" href="ftp://ftp.ripe.net/rfc/rfc3596.txt"> RFC 3596 insert: </a> ] "DNS Extensions to Support IP Version 6", [ insert: <a class="external-link" href="ftp://ftp.ripe.net/rfc/rfc3363.txt"> RFC 3363 insert: </a> ] “Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System”, [ insert: <a class="external-link" href="ftp://ftp.ripe.net/rfc/rfc3364.txt"> RFC 3364 insert: </a> ] “Tradeoffs in Domain Name System mapping can also (DNS) Support for Internet Protocol version (IPv6)” insert: 

insert: <h3>

insert: `<a name="attribution">` insert: `</a>` 6.0 Attribution insert: `</h3>`

insert: 

This document is compiled from policies developed by the RIPE community. insert: 

insert: 

The following people actively contributed to this policy by making proposals through the RIPE Policy Development Process: insert: 

insert: 

Olaf Kolkman
be delegated in a similar model as used for the normal Domain delete:   Name System. For instance, the RIPE NCC has been assigned the delete:   complete class C address space starting with 193. It is there- delete:   fore possible to delegate the 193.in-addr.arpa domain completely delete:   to the RIPE NCC, instead of each and every reverse mapping in the delete:   193.in-addr.arpa domain to be registered with the INTERNIC. This delete:   implies that all 193.in-addr.arpa resistrations will be done by delete:   the RIPE NCC. Even better, since service providers receive com- delete:   plete class C network blocks from the RIPE NCC, the RIPE NCC can delete:   delegate the reverse registrations for such complete blocks to delete:   these local registries. This implies that customers of these delete:   service providers no longer have to register their reverse domain delete:   mapping with the root, but the service provider have authority delete:   over that part of the reverse mapping. This decreases the work- delete:   load on the INTERNIC and the RIPE NCC, and at the same time in- delete:   crease the service a provider can offer its customers by improve delete:   response times for reverse mapping changes . However there are delete:   some things that need to be examined a bit more closely to avoid delete:   confusion and inconsistencies. These issues are covered in the delete:   next section. delete:   delete:   delete:   Procedures for the delegation of direct subdomains of 193.in- delete:   addr.arpa delete:   delete:   1. A secondary nameserver at ns.ripe.net is mandatory for all delete:   blocks of class C network numbers delegated in the 193.in- delete:   addr.arpa domain. delete:   delete:   2. Because of the increasing importance of correct reverse ad- delete:   dress mapping, for all delegated blocks a good set of secondaries delete:   must be defined. There should be at least 2 nameservers for all delete:   blocks delegated, excluding the RIPE NCC secondary. delete:   delete:   3. The delegation of a class C block in the 193.in-addr.arpa delete:   domain can be requested by sending in a domain object for the delete:   RIPE database to <[email protected]> with all necessary contact delete:   and nameserver information. The RIPE NCC will then forward all delete:   current reverse zones inside this block to the registry, and delete:   after addition of these by the registry, the NCC will check the delete:   working of the reverse server. Once everything is setup proper- delete:   ly, the NCC will delegate the block, and submit the database ob- delete:   ject for inclusion in the database. An example domain object can delete:   be found at the end of this document. delete:   delete:   4. All reverse servers for blocks must be reachable from the delete:   whole of the Internet. In short, all servers must meet similar delete:   connectivity requirements as top-level domain servers. delete:   delete:   5. Running the reverse server for class C blocks does not imply delete:   that one controls that part of the reverse domain, it only im- delete:   plies that one administers that part of the reverse domain. delete:   delete:   6. Before adding individual nets, the administrator of a reverse delete:   domain must check wether all servers to be added for these nets delete:   are indeed setup properly. delete:   delete:   7. There are some serious implications when a customer of a ser- delete:   vice provider that uses address space out of the service provider delete:   class C blocks, moves to another service provider. The previous delete:   service provider cannot force its ex-customer to change network delete:   addresses, and will have to continue to provide the appropriate delete:   delegation records for reverse mapping of these addresses, even delete:   though it they are no longer belonging to a customer. delete:   delete:   8. The registration of the reverse zones for individual class C delete:   networks will usually be done by the registry administering the delete:   class C block this network has been assigned from. The registry delete:   will make the necessary changes to the zone, and update the net- delete:   work objects in the RIPE database for these networks, to reflect delete:   the correct "rev-srv" fields. In case the RIPE NCC receives a delete:   request for the reverse zone of an individual class C network out delete:   of a block that has been delegated, the request will be forwarded delete:   to the zone contact for this reverse block. delete:   delete:   9. The NCC advises the following timers and counters for direct delete:   subdomains of 193.in-addr.arpa: 8 hours refresh (28800 seconds), delete:   2 hours retry (7200 seconds), 7 days expire (604800 seconds) and delete:   1 day Time To Live (86400 seconds). The retry counter should be delete:   lowered where connectivity is unstable. delete:   delete:   Above procedures are defined to ensure the necessary high availa- delete:   bility for the 193 reverse domains, and to minimize confusion. delete:   The NCC will ensure fast repsonse times for addition requests, delete:   and will in principle update the 193.in-addr.arpa domain at least delete:   once per working day. delete:   delete:   Example domain object to request a block delegation delete:   delete:   domain: 202.193.in-addr.arpa delete:   descr: Pan European Organisations class C block delete:   admin-c: Daniel Karrenberg delete:   tech-c: Marten Terpstra delete:   zone-c: Marten Terpstra delete:   nserver: ns.eu.net delete:   nserver: sunic.sunet.se delete:   nserver: ns.ripe.net delete:   changed: [email protected] 930319 delete:   source: RIPE delete:   delete:   delete:   delete:   Procedures for the delegation of individual network zones by the delete:   RIPE NCC. delete:   delete:   The registration of the reverse zones for individual class C net- delete:   works will usually be done by the registry administering the delete:   class C block this network has been assigned from. In case the delete:   zone corresponding to the class C block has not been delegated, delete:   the RIPE NCC will automatically add the reverse nameserver as delete:   specified in the "rev-srv" attribute of the RIPE database object delete:   for this network, using the following procedures: delete:   delete:   1. Because of the increasing importance of correct reverse ad- delete:   dress mapping, for all delegated networks a good set of secon- delete:   daries must be defined. There should be at least two nameservers delete:   for all networks delegated. delete:   delete:   2. The "rev-srv" field should ONLY contain one fully qualified delete:   domain name of a nameserver which is authoritative for the re- delete:   verse zone for this network. delete:   delete:   3. If a network has or is going to have any external connectivi- delete:   ty, it is strongly recommended that it has at least one reverse delete:   nameserver that can be reached from all of the Internet. delete:   delete:   4. The checking and addition of the reverse zones for single net- delete:   works is completely automated at the RIPE NCC. Although we do delete:   our best to check the setup of the nameservers, these does not delete:   receive the same level of scrutiny as nameservers for blocks of delete:   class C network numbers. It is the responsibility of the network delete:   contacts to ensure proper operation. delete:   delete:   5. Any problems regarding the reverse zones in 193.in-addr.arpa delete:   should be directed to <[email protected]>. delete:   delete:   The NCC also suggests that similar procedures are set up for the delete:   delegation of reverse zones for individual class C networks from delete:   the registries to individual organisations. delete:  Leo Vegoda insert: 

Guidelines Policy For The Reverse Address Delegation Of Zones In The 193.in-addr.arpa Domain of IPv4 and IPv6 Address Space in the RIPE NCC Service Region

RIPE Documents Search

ripe-085

State:

Obsoleted

Updated by:

ripe-105 , ripe-127 , ripe-136 , ripe-140 , ripe-159 , ripe-185 , ripe-234 , ripe-245 , ripe-263 , ripe-288 , ripe-301 , ripe-302 , ripe-324 , ripe-368 , ripe-387 , ripe-389 , ripe-405 , ripe-411 , ripe-424 , ripe-441 , ripe-448 , ripe-449 , ripe-463 , ripe-471 , ripe-484 , ripe-492 , ripe-496 , ripe-498 , ripe-509 , ripe-515 , ripe-524 , ripe-525 , ripe-527 , ripe-528 , ripe-530 , ripe-553 , ripe-577 , ripe-579 , ripe-581 , ripe-582 , ripe-592 , ripe-595 , ripe-599 , ripe-604 , ripe-606 , ripe-621 , ripe-622 , ripe-623 , ripe-628 , ripe-632 , ripe-634 , ripe-638 , ripe-643 , ripe-648 , ripe-649 , ripe-654 , ripe-667 , ripe-679 , ripe-680 , ripe-689 , ripe-695 , ripe-708 , ripe-709 , ripe-720 , ripe-725 , ripe-730 , ripe-733 , ripe-758

Authors:

Marten Terpstra

Date:

May 1993

Download

File:
ASCII | 8.0KB

Changes to Guidelines For The Delegation Of Zones In The 193.in-addr.arpa Domain

Contents insert: </h3>

insert: <a name="definition"> insert: </a> 1.0 Definition insert: </h3>

insert: <a name="introduction"> insert: </a> 2.0 Introduction insert: </h3>

insert: <a name="reverse_delegation"> insert: </a> 3.0 Reverse Delegation in the RIPE NCC Service Region insert: </h3>

insert: <a name="procedures"> insert: </a> 4.0 Procedures insert: </h3>

insert: <a name="references"> insert: </a> 5.0 References insert: </h3>

insert: <a name="attribution"> insert: </a> 6.0 Attribution insert: </h3>

RIPE Documents Search

ripe-085

Contents insert: `</h3>`

insert: `<a name="definition">` insert: `</a>` 1.0 Definition insert: `</h3>`

insert: `<a name="introduction">` insert: `</a>` 2.0 Introduction insert: `</h3>`

insert: `<a name="reverse_delegation">` insert: `</a>` 3.0 Reverse Delegation in the RIPE NCC Service Region insert: `</h3>`

insert: `<a name="procedures">` insert: `</a>` 4.0 Procedures insert: `</h3>`

insert: `<a name="references">` insert: `</a>` 5.0 References insert: `</h3>`

insert: `<a name="attribution">` insert: `</a>` 6.0 Attribution insert: `</h3>`