Changes to ARIN inaddr.arpa zone generation process

[RIPE NCC Staff <]

[Apologies for duplicate messages]


      CHANGES TO ARIN IN-ADDR.ARPA ZONE GENERATION PROCESS

Please not the information in the message below from Ginny Listman,
Director of Engineering at ARIN, the American Registry for Internet
Numbers. The message relates to changes in the generation of the
in-addr.arpa zone files by ARIN.

This information is specifically pertinent to organisations with
networks currently reverse-delegated by ARIN. Please note that this
does not directly affect organisations with networks reverse-delegated
by the RIPE NCC.


Kind regards,

RIPE NCC

+------------------------------------------------+
| RIPE NCC (Network Co-ordination Centre)        |
| ncc@localhost                                 |
|                                                |
| http://www.ripe.net                            |
| Singel 258, 1016 AB Amsterdam, The Netherlands |
| Tel: +31-20-5354444                            |
| Fax: +31-20-5354445                            |
+------------------------------------------------+

-----Begin Forwarded Message -----
 From: On Behalf Of ARIN IN-ADDR Role inaddr@localhost
 Sent: Thursday, May 17, 2001 4:18 PM
 To: arin-announce@localhost
 Cc: nanog@localhost
 Subject: in-addr.arpa zone generation process to change


When ARIN began operations, one of the tasks that it took over
from the InterNIC was the generation of the zone file for the
in-addr.arpa domain. In order to correct long-standing issues
with the data in the zone file, new software is being deployed. 

ARIN policy states that allocation subscribers with networks 
of /16 or shorter prefix are responsible for maintaining all 
in-addr.arpa domain records for reassignments within the block.
They must also provide to ARIN the host names of the 
nameservers hosting any delegations. ARIN will continue to 
host domain records for delegations of networks with prefixes 
longer than /16.

The in-addr.arpa zone will contain delegations for any /8 
containing nameservers within ARIN's database. For address 
space not covered via these delegations, the in-addr.arpa 
domain will contain delegations for /16's with nameservers.  
For address space still not delegated and as mentioned above, 
the in-addr.arpa domain will contain delegations of /24's for 
networks longer than a /16 containing in-addr nameservers.  
In all cases, the most specific reassignment with nameservers 
at each octet boundary will prevail.

ARIN is making every effort to ensure that any impact from 
these changes will not disrupt in-addr.arpa name services.  
If you have concerns whether in-addr.arpa name services will 
be impacted for your networks, please review examples of the 
changes to occur at:

    http://www.arin.net/inaddr/inaddr-examples.txt

If you still have concerns after reviewing these examples, 
please direct specific questions about your networks to 
inaddr@localhost.  We have tentatively scheduled implementation
of the new process for late May or early June. A specific date 
will be announced several days prior to the cut-over on both 
the arin-announce and nanog mailing lists.

Regards,

Ginny Listman
Director of Engineering
ARIN

-----End Forwarded Message -----