FAQ: Reverse Delegation

Show/Hide all

I have created the in-addr.arpa domain object corresponding to my IP range in the RIPE Database, but this zone is still not delegated to my name servers. →

Please allow up to six hours, after the creation of the Domain object in the RIPE Database, for the zone to be delegated. If after this period the zone is still not delegated, please send an e-mail to <ripe-dbm@ripe.net> with the details of your zone, as well as a reference to the domain object present in the RIPE Database.

When I request the reverse delegation for my ASSIGNED PI IP range, I receive the an authentication error. →

If you receive an authentication error as follows:

***Info: Authorisation for parent [inetnum] XXX.XXX.XXX.XXX - XXX.XXX.XXX.XXX using mnt-lower: not authenticated by: RIPE-NCC-HM-PI-MNT

You are being asked for authorisation from the 'mnt-lower: RIPE-NCC-HM-PI-MNT' field that is present in your ASSIGNED PI inetnum object. In order to bypass this, you should add the following line to your inetnum object:

mnt-domains: [your own maintainer]

This will give the above maintainer the authorisation for requesting the reverse delegation for this IP range.

How can I request reverse delegation for my ASSIGNED PI IP range which is smaller than a /24? →

If your IP range is: X.Y.Z.A - X.Y.Z.B, please create the following SOA record in your name servers:

A-B.Z.Y.X.in-addr.arpa

Afterwards, send the domain object A-B.Z.Y.X.in-addr.arpa to <ripe-dbm@ripe.net>.

We will delegate the above zone to your name servers. Additionally, we will create CNAME records in our name servers for each of the corresponding IP addresses in this range, as follows:

A.Z.Y.X.in-addr.arpa. 432000 IN CNAME A.A-B.Z.Y.X.in-addr.arpa
[...]
B.Z.Y.X.in-addr.arpa 432000 IN CNAME B.A-B.Z.Y.X.in-addr.arpa

From this point on, you can create your PTR records as:

[address].A-B.Z.Y.X.in-addr.arpa

I use ns.ripe.net as a secondary name server, but it is no longer refreshing my zone after I changed the IP address(es) of my master name server. →

Our provisioning system looks up the IP address(es) of your master name server when you submit a domain object to the RIPE Database. If you subsequently change your IP address(es), ns.ripe.net will not notice this. You need to refresh your domain object in the RIPE Database (by adding a changed: attribute, for example) to force our provisioning system to notice the new IP address(es).