Dear all, As of today the RIPE NCC offers an automated method for the submission of reverse zone delegations in 193.in-addr.arpa and 194.in-addr.arpa. Your delegation requests and the zone files on all nameservers will be checked automatically. The diagnostics generated by these checks will be returned to you automatically too. This will make you aware of any problems very quickly, so that you can correct them and re-submit your request. When the automated procedure does not detect any errors, the request is forwarded to the inaddr role account person for some additional manual checks and the processing of the delegation itself. Of course, you will receive an acknowledgement when this has been done. To use the new automated procedure send your request in ripe-105 format to: <auto-inaddr@ripe.net> 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. HELP - will send you a (patched) ripe-105 document CHANGE - is needed if you want to change an existing reverse delegation LONGACK - will give you the most verbose output as possible RIPE document ripe-105 requires you to send in a RIPE database 'inetnum' object with a 'rev-srv' attribute for each nameserver for single/multiple C's reverse delegation requests and for whole blocks 'domain' objects with 'nserver' attributes for each nameserver. I recommend to use the following procedure for doing your request: Send an E-mail to <auto-inaddr@ripe.net> with LONGACK in the 'Subject:' line and an appropriate RIPE database object as described in ripe-105 in the body of the message. We still accept the old method for reverse delegation requests (ripe-105 format request to <inaddr@ripe.net>), however it might take some more time to process them. After some time, when the software doesn't change daily anymore, the source code will be published. I am neither a DNS expert or native English writer ;-) so all your comments are welcome! Please send them together with complaints, bug reports or special requests to <inaddr@ripe.net>. Kind regards, David Kessens RIPE NCC