Skip to main content
  • Legend
  • Added
  • Deleted

Contents

1.0 Definitions Link: #definitions

2.0 Introduction Link: #introduction

3.0 Transfer of Internet Number Resources Link: #transfer

3.1 Submission of the Request for Transfer Link: #transfer31

3.2 If the Receiving Party is not a Member Link: #transfer32

3.3 Financial Consequences Link: #transfer33

3.4 Internet Number Resource Registration and RIPE Database Issues Link: #transfer34

3.5 Transfers between LIR accounts belonging to the same member Link: #transfer35

4.0 Member Changes Official Legal Name Link: #memberchanges

1.0 Definitions

For the purposes of this document, Internet number resources refer to:

  • The registered allocation and assignment records of a member
  • The independent Internet number resource records assigned to an End User through a member acting as a sponsoring LIR

2.0 Introduction

In order for the RIPE NCC to maintain an accurate registry, it must hold accurate data concerning:

  • The natural or legal persons holding the registration of Internet number resources
  • The Internet number resources that are registered to these natural or legal persons

This means that any transfer of Internet number resources from one party to another, or any change to the legal status of a party holding the registration of Internet number resources, must be communicated to the RIPE NCC.

A member must inform the RIPE NCC if one or both of the following changes occurs:

  1. Internet Number Resource are transferred. Such transfers may take place:
  2. The member changes its official legal name. Such a change may occur, for example, because of a merger or acquisition of the member's organisation.
European Internet Registry: Procedures for DNS Delegation in the IN-ADDR.ARPA Domain David Kessens June 1994 Document-ID: ripe-105++ Obsoletes: ripe-105 ABSTRACT

This document describes the procedures for such changes to be properly communicated and registered with the RIPE NCC.

Note:

If a change in a member's official legal name is accompanied by a transfer of Internet number resources, the member must first inform the RIPE NCC of the name change and then of the transfer.

If a change in a member's business structure is not accompanied by a transfer of Internet number resources or a change in the member's official legal name, then the RIPE NCC does not need to be informed of this change.

This document does not describe the procedure to be followed in the case of changes with regards to independent Internet number resources assigned to End Users or any changes to the End Users business structure. This procedure is described in the RIPE NCC Procedural Document, “Independent Internet Number Resources – Contractual Relationship Changes Between Sponsoring LIR and End User Link: https://www.ripe.net/publications/docs/lir-end-user-contractual-changes ”.

This document does not describe the procedure to be followed in case of a transfer of Internet number resources from the RIPE NCC service region to the service region of another RIR and vice versa. This procedure is described in the RIPE NCC procedural document, “Inter-RIR Transfer of Internet Number Resources Link: https://www.ripe.net/publications/docs/inter-rir-transfer-of-inr ”.

3.0 Transfer of Internet Number Resources

If a member transfers their Internet number resources to a third party for any reason, this transfer must be declared to the RIPE NCC for approval.

3.1 Submission of the Request for Transfer

For the transfer to be processed, one of the involved parties must submit a request to the RIPE NCC:

A registered contact or an authorised person (e.g., senior manager, legal successor) must send the request.

The RIPE NCC will ask for the following information:

i. Information regarding the parties involved, including:

  • The full official legal names of all parties involved
  • Which party will transfer the Internet number resources and which party will receive them
  • Recent registration papers issued by the relevant national authorities for all involved parties

If the current official legal names of the involved members are different from those in the relevant signed RIPE NCC Standard Service Agreement, then the procedure described in Section 4.0 Link: #memberchanges must be followed prior to the transfer of the Internet number resources.

The procedure described under Section 4.0 is not necessary for the transferring member if the RIPE NCC Standard Service Agreement for that member is terminated (see Sections A.1.1 and A.1.2 of the RIPE NCC Procedural Document, “Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: https://www.ripe.net/publications/docs/closure ”.

ii. A description of the reason for the transfer (for example, due to merger, acquisition, transfer of Internet number resources according to the RIPE policies)

If the transfer is taking place due to a change in the structure of the organisation(s) involved (e.g., merger, acquisition), a description of the changes among these organisation(s) is necessary. This description must be accompanied by the official legal documents issued by the relevant national authorities proving/supporting the changes the request is based on.

If the change in the structure of the organisation(s) involved cannot be proven/supported by official documentation from national authorities describing this change (e.g., a network acquisition from one member to another), then these cases will fall within the scope of the relevant RIPE Policies (Section 5.5 and 6.4 of “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Link: https://www.ripe.net/publications/docs/ipv4-policies ”, Section 8 of “IPv6 Address Allocation and Assignment Policy Link: https://www.ripe.net/publications/docs/ipv6-policy ” and Section 4.0 of “Autonomous System (AS) Number Assignment Policies Link: https://www.ripe.net/publications/docs/asn-assignment-policies ”) and will be evaluated in accordance with them.

iii. A list of the Internet number resources that are requested to be transferred. If all of the transferring member's Internet number resources registered are being transferred, a confirmation of this is requested.

The member must also indicate any End User assignment agreements that are requested to be transferred.

If a member transfers all of their Internet number resources, their RIPE NCC Standard Service Agreement may be terminated (see Section A.1.1. of the RIPE NCC Procedural Document, “Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources Link: http://www.ripe.net/publications/docs/closure ”).

iv. The correct contact details of all parties involved

The RIPE NCC may ask the parties involved to confirm the correctness of their contact details or to update them. The contact details include the billing contact details and the VAT number details.

v. A Transfer Agreement signed by both parties or by their legal successors

The RIPE NCC provides the template of the Transfer Agreement that either party may submit to the RIPE NCC.

The Transfer Agreement must be signed by authorised persons for both parties. For the transferring party, it is required that the Transfer Agreement is signed by an authorised representative having the general capacity to act on behalf of this party. The RIPE NCC reserves the right to request official documentation proving that the person signing on behalf of either party is authorised to do so.

The RIPE NCC may ask the other party/parties to confirm their agreement to the transfer. The confirmation must be authorised (signed or sent) by a contact person or authorised person (e.g., senior manager, legal successor).

If the transferring party no longer exists by the time the RIPE NCC is being informed, the receiving party must send:

  • An official document (issued by a national authority) confirming the closure of the transferring party
  • A copy of an older signed agreement between the relevant parties mentioning the transfer of the Internet number resources. If such an agreement is not available, the RIPE NCC may accept a confirmation of the transfer to the RIPE NCC signed by an authorised person (e.g., senior manager, legal successor) of the receiving party. The RIPE NCC reserves the right to reverse the transfer should another party object and provide an agreement that proves that the Internet number resource should have been transferred to them.

vi. An overview of the utilisation of all allocations and of the status of all independent Internet number resource assignments

The RIPE NCC may ask for an overview of the utilisation of all Internet number resources registered to the member and of all End User assignment agreements signed by the member.

3.2 If the Receiving Party is not a Member

Members may wish to transfer their Internet number resource to another member or to a third party that is not a member.

If the Internet number resources are transferred to a non-member, the receiving party must apply to be a member by signing a RIPE NCC Standard Service Agreement before the transfer takes place (more information on how to become a member is available Link: https://www.ripe.net/become-a-member ). If the receiving party refuses to do the above, the RIPE NCC will not transfer the Internet number resources to them.

If the Internet number resources to be transferred are Provider Independent (PI) addresses, the receiving party may either apply to become a member by signing the RIPE NCC Standard Service Agreement, or can enter into a contractual relationship with a sponsoring LIR. For more information, please see the notes on Requesting Independent Resources Link: https://www.ripe.net/participate/resource-management/independent-resources .

The request for the transfer can be submitted as described above (Section 3.1).

3.3 Financial Consequences

All outstanding invoices and all outstanding financial obligations must be paid in full. If the RIPE NCC Standard Service Agreement is terminated in the course of the RIPE NCC financial year, the service fee for this member must be paid for the full year. This payment is the responsibility of the receiving member. If the receiving party is not a member, then payment is the responsibility of the transferring member.

If the receiving party decides to sign the RIPE NCC Standard Service Agreement, then a sign-up fee must be paid (see RIPE NCC Charging Scheme Link: http://www.ripe.net/publications/docs/charging ).

3.4 Internet Number Resource Registration and RIPE Database Issues

The RIPE NCC will review the status of any IP address allocation or independent Internet number resource assignment maintained by the party involved, in compliance with the RIPE Policies current at the time of the transfer.

The receiving member must deregister from the RIPE Database any invalid or overlapping registrations or unused assignment approvals.

The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The transferring member must update all RIPE Database objects maintained by them that are related to this transfer.

3.5 Transfers between LIR accounts belonging to the same member

Transfers of Internet number resources between LIR accounts belonging to the same member fall within the scope of the relevant RIPE Policies (Section 5.5 and 6.4 of “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Link: https://www.ripe.net/publications/docs/ipv4-policies ”, Section 8 of “IPv6 Address Allocation and Assignment Policy Link: https://www.ripe.net/publications/docs/ipv6-policy ” and Section 4.0 of “Autonomous System (AS) Number Assignment Policies Link: https://www.ripe.net/publications/docs/asn-assignment-policies ”) and will be evaluated in accordance with them.

The procedure described above in Section 3.1 is applicable except from paragraphs 3.1.ii and 3.1.v.

If after the transfer the member decides to close an LIR account, all outstanding invoices and all outstanding financial obligations for this LIR account must be paid in full.

The RIPE NCC will review the status of any IP address allocation or independent Internet number resource assignment maintained by the member, in compliance with the RIPE Policies current at the time of the transfer.

The member must deregister from the RIPE Database any invalid or overlapping registrations.

The RIPE NCC will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this transfer. The member must update all RIPE Database objects maintained by them that are related to this transfer.

4.0 Member Changes Official Legal Name

It is the obligation of the member to inform the RIPE NCC immediately if any change in the member's official legal name occurs.

The member must send an email to ncc@ripe.net Link: mailto:ncc@ripe.net informing the RIPE NCC of the name change. This email must include:

  • New registration papers from the national authority; and
  • The official legal documents supporting this change

The RIPE NCC will send a new RIPE NCC Standard Service Agreement Link: http://www.ripe.net/publications/docs/service-agreement for the member to sign under the new official legal name. When the RIPE NCC receives the new RIPE NCC Standard Service Agreement properly signed by the member, it will update the registry, including all RIPE Database objects maintained by the RIPE NCC that are related to this change. The member must update all RIPE Database objects maintained by them that are related to this change.

If the change in the member's official legal name occurred without a further change in the member's structure (e.g., merger with another legal entity, acquisition by/of another legal entity), the member will not have to sign a new RIPE NCC Standard Service Agreement.

the delegation of zones in European subdomains of IN-ADDR.ARPA. Introduction The domain tree below IN-ADDR.ARPA is used to facilitate "reverse" mapping from IP addresses to domain names [RFC883, RFC1033]. This document describes the procedures for the delegation of zones in European subdomains of IN-ADDR.ARPA. Randomly Assigned Numbers There are two groups of European network numbers: hierarchically assigned numbers and randomly assigned ones. The hierarchically assigned numbers are part of the 193.x.y.0 and 194.x.y.0 network blocks. All other European network numbers, class A, class B and 192.x.y.0 class Cs are randomly assigned. Hierarchically Assigned Numbers The subdomains of IN-ADDR.ARPA corresponding to the hierarchically assigned network numbers are administered by the RIPE NCC. These numbers are currently: 193.0.0.0 - 194.255.255.255 The other addresses are administered by the other regional registries that might have other procedures for requesting a reverse delegation. For clarity we refer in the procedures and examples as described below to the 193.x block of addresses, although we could have as well used the other block(s) that RIPE administers. With the assignment of class C network numbers following RFC1466, large chunks of the address space are delegated to regional Internet Registries. The regional registries delegate blocks of class C net- work numbers to local Internet Registries. In this way a hierarchy in the address space is created, which is similar to the hierarchy in the domain name space. Due to this hierarchy the reverse DNS map- ping can also be delegated in a similar model as used for the normal Domain Name System. For instance, the RIPE NCC has been delegated the complete class C address space starting with 193. It is therefore possible to delegate the 193.IN-ADDR.ARPA domain completely to the RIPE NCC, instead of each and every reverse mapping in the 193.IN-ADDR.ARPA domain to be registered with the InterNIC. This implies that all 193.IN-ADDR.ARPA delegations in turn will be done by the RIPE NCC. Even better, since local registries usually receive blocks of 256 class C networks from the RIPE NCC, the NCC can delegate the reverse registrations for such complete blocks to these local registries. This implies that customers of these service providers no longer have to register their reverse domain mapping with the InterNIC or the NCC, but the service providers have authority over that part of the reverse mapping. This decreases the workload on the InterNIC and the RIPE NCC, and at the same time improves the service a provider can offer its customers by improving response times for reverse mapping changes. In order to provide a reliable service some procedures have been agreed and must be followed in order to avoid confusion and inconsistencies. These procedures are covered in the procedure section. The registration of the reverse zones for individual class C net- works will usually be done by the registry administering the class C block this network has been assigned from. If the subdomain has not yet been delegated to the registry con- cerned the RIPE NCC will register the individual networks. However this service is only provided at a "best-effort" level and no ser- vice guarantees are given. The local registries should whenever possible provide this service locally. Responsibilities for the DNS administrator of a reverse block delegation: As with all domain name space, running the reverse server for class C blocks does not imply that one controls that part of the reverse domain. It only implies that one administers that part of the reverse domain. If after repeated complaints the delegated name space is still not administered properly the RIPE NCC has to revoke the delegation. Before adding individual nets, the administrator of a reverse domain must check whether all servers to be added for these nets are indeed set up properly. There are some serious implications when a customer that uses address space out of the service provider class C blocks, moves to another service provider. The previous service provider cannot force its ex-customer to change network addresses, and will have to continue to provide the appropriate delegation records for reverse mapping of these addresses, even though they are no longer belonging to a customer. The registration of the reverse zones for individual class C networks will usually be done by the registry administering the class C block this network has been assigned from. The registry will make the necessary changes to the zone files. The registry will also make sure that the network objects in the RIPE database for these networks are updated with the correct "rev-srv" attributes. In case the RIPE NCC receives a request for the reverse zone of an individual class C network out of a block that has been delegated, the request will be forwarded to the mailbox speci- field in the SOA RR for the zone concerned and to the zone- contact registered in the RIPE database for that zone. The NCC also suggests that similar procedures are set up for the delegation of reverse zones for individual class C networks from the registries to individual organisations. Procedures The procedure for asking the reverse delegation of a block (256 C's) of addresses or network (1 or more C's) addresses is quite similar but there are some differences. Therefor they are described as one procedure with clear remarks when something only applies for block or network delegations. Note that we will be a little bit more stringent on the rules for block delegations since we need to be sure that other people can rely on you for proper operation of the DNS system. Above procedures are defined to ensure the necessary high availabil- ity for the reverse domains, and to minimise confusion. The NCC will ensure fast response times for addition requests, and will in principle update the 193.IN-ADDR.ARPA domain at least once per working day, if needed. Any problems regarding the reverse zones in 193.IN-ADDR.ARPA should be reported to <inaddr@ripe.net>. 1. We only reverse delegate when all addresses are assigned to you. 2. Your nameservers should be configured and running and should have good reachability on the internet. Nameservers for block delegations must meet similar connectivity requirements as top-level domain servers. The NCC recommends to use the following timers and counters (as advised by RFC1537): 28800 ;refresh period (8 hours) 7200 ;retry interval (2 hours) 604800 ;expire time (1 week) 86400 ;default ttl (1 day) It is mandatory for network (C) reverse delegations: - ns.ripe.net is NOT one of the secondary/primary nameservers - at least two nameservers should be used - We need a RIPE database 'inetnum' object with 'rev-srv:' attributes for the name (not IP address) of each nameserver. It is mandatory for block reverse delegations: - ns.ripe.net is one the secondary (never primary) nameservers - at least two other nameservers that don't reside on the same ethernet are required - Operators of the primary nameservers should be familiar with RFC1537 and this document - We need a RIPE database 'domain' object for each delegation with 'nserver:' attributes for the name (not IP address) of each nameserver 3. Send an E-mail request to <auto-inaddr@ripe.net> with: - In the header (or body if not possible) of your E-mail message: X-NCC-RegID: Country.RegistryName This is not required, though easy for keeping track of the requests. Of course, we don't need your local registry ID if you are not from a RIPE local registry. For network (C) reverse delegations: - We need a RIPE database 'inetnum' object with 'rev-srv:' attributes for the name (not IP address) of each nameserver For block reverse delegations: - State in your request that you know about RFC1537 & this document - A RIPE database 'domain' object for each delegation with 'nserver:' attributes for the name (not IP address) of each nameserver 4. Your request will first go through to an automatic checking program. The program will check your zone files and report you about errors (that should be fixed), warnings (that you might want to change), or that no errors have been found. If errors are found, you will be asked to fix them and resubmit your request and the automatic checks will be done again. If no errors (warnings are allowed, but we strongly suggest that you at least take a look at them) are found your request will be acknowledged and your request will be forwarded to the person in charge of the reverse delegation requests. He/she processes the request further. If no additional problems are found the object will included in the database and the block/network reverse delegated. You will always receive an acknowledgment when the delegation has been done or an explanation why not. Example of a network delegation request: From: "Anne X. Ample" <anne.x.ample@ample.nl> To: RIPE Hostmaster <auto-inaddr@ripe.net> Subject: LONGACK 2.1.193.in-addr.arpa delegation please Please delegate 2.1.193.in-addr.arpa as specified below. Thank you! For the AMPLE Corporation Anne X. Ample inetnum: 193.1.2.0 - 193.1.3.255 netname: AMPLE descr: AMPLE Corporation descr: Amsterdam, Netherlands country: NL admin-c: Anne X. Ample tech-c: G. E. K. Ample aut-sys: 4711 rev-srv: ns.ample.nl rev-srv: ns.elpma.ln changed: anne.x.ample@ample.nl 930101 source: RIPE Example of a block (256 C's) reverse delegation: From: Marten Terpstra <marten@in.ter.net> To: RIPE Hostmaster <auto-inaddr@ripe.net> Subject: LONGACK 202.193.in-addr.arpa delegation please Dear NCC people, I have read and understood ripe-105++ and RFC1537. Could you please delegate 202.193.in-addr.arpa as specified below. Thank you! Marten Terpstra domain: 202.193.in-addr.arpa descr: Pan European Organisations class C block admin-c: Daniel Karrenberg tech-c: Marten Terpstra zone-c: Marten Terpstra nserver: ns.eu.net nserver: sunic.sunet.se nserver: ns.ripe.net changed: marten@ripe.net 930319 source: RIPE Some notes on the automatic checking program: You can use some keywords in the 'Subject:' line of your E-mail to control the checking process. The use of the LONGACK keyword is very recommended. For changing an existing delegation put the keyword CHANGE in the 'Subject:' line of your E-mail message. HELP - will send you this document CHANGE - is needed if you want to change an existing reverse delegation LONGACK - will give you the most verbose output as possible TEST - will only test your zone files without actually doing the request When you want to to a request for a block delegation and you want to know if there are already reverse zones registered within the zone of the requested block delegation, just send in your request and you will receive an error report that includes a copy of our zone file regarding this zone!