[ncc-services-wg] New Policy and Procedures for Reverse DNS Requests

Dear Colleagues,

(Apologies for duplicate messages)

The RIPE NCC has implemented a number of changes in the policy and
procedures for requesting reverse delegation. This follows the effort
to streamline reverse DNS operations [1] and make it easier for
network administrators to manipulate related DOMAIN objects.

You should be aware of the following changes:

When users want to update their reverse DNS information, they send an
e-mail to <auto-dbm at ripe.net> (formerly this mail was sent to
<auto-inaddr at ripe.net>). The database update program will verify the
DNS information and update the RIPE Database. The information will
appear in the DNS after a short delay.

The policy constraints have been reduced. Previously only space
assigned to End Users could be reverse delegated in DNS. This caused
administrative burden to LIRs, as every time space was assigned,
reverse DNS had to be set up for that space. Now reverse DNS can be
set up for an entire allocation.

Documentation that details the new setup and authorisation can be found at:

http://www.ripe.net/reverse/

More details on these developments is provided below.

* The reverse DNS policy as proposed in [3] is published as ripe-xxx.

The main change to the policy is the removal of the requirement for
valid assignments.

Reverse delegations can also be requested by non LIRs if an
appropriate "mnt-domains:" attribute is in place in the corresponding
INETNUM/INET6NUM object, when submitting requests to
<auto-dbm at ripe.net>.

* The <auto-inaddr at ripe.net> interface will be deprecated as of 1 July 2004.

To allow for a graceful transition, the "mnt-domains:" based
authorisation mechanism has not been implemented for the
<auto-inaddr at ripe.net> interface. This will continue to use reg ID
based authorisation.

The "mnt-by:" attribute will become mandatory. However, the existence
of the "mnt-by:" attribute in DOMAIN objects is not enforced when the
object is submitted through the <auto-inaddr at ripe.net> interface.

Please contact <inaddr at ripe.net> if you have further questions.

Olaf Kolkman
New Projects, RIPE NCC

Can Bican
Software Engineering Dept., RIPE NCC

----------------------------------------------------------------------


References:

[1] Original RDNS Project Proposal
http://www.ripe.net/reverse/proposal.html

[2] "mnt-domains:" Attribute Proposal
http://www.ripe.net/ripe/mail-archives/dns-wg/2004/msg00007.html

[3] Policy for Reverse Address Delegation of IPv4 and IPv6 Address
Space in the RIPE NCC Service Region
http://www.ripe.net/ripe/docs/rev-del.html

[4] Webupdates
http://www.ripe.net/perl/webupdates.pl

[5] http://www.ripe.net/ripe/mail-archives/dns-wg/2004/msg00008.html