[apops] in-addr.arpa zone generation process to change (fwd from ARIN)

  • To: apnic-announce at lists dot apnic dot net
  • Subject: [apops] in-addr.arpa zone generation process to change (fwd from ARIN)
  • From: APNIC Secretariat <secretariat at apnic dot net>
  • Date: Thu, 24 May 2001 17:42:17 +1000 (EST)
  • Cc: apops at lists dot apnic dot net
  • Sender: owner-apops@lists.apnic.net
    • 
      	IMPORTANT OPERATIONAL ADVICE FOR ORGANISATIONS WITH
      	NETWORKS CURRENTLY REVERSE-DELEGATED BY ARIN.
      
      The following message contains information relating to forthcoming changes
      in the generation of in-addr.arpa zone files by ARIN, the American
      Registry for Internet Numbers.  
      
      Please note that it does not directly affect reverse delegations
      held/generated by APNIC.
      
      Regards,
      
      Anne Lord
      APNIC 
      
      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      APNIC Secretariat
      <secretariat at apnic dot net>
                                                           Tel: +61-7-3367-0490
      Asia Pacific Network Information Centre (APNIC) Ltd  Fax: +61-7-3367-0482
      Level 1, 33 Park Road, PO Box 2131, Milton, QLD 4064, Australia
      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      
      -----Begin Forwarded Message -----
       From: On Behalf Of ARIN IN-ADDR Role <inaddr at arin dot net>
       Sent: Thursday, May 17, 2001 4:18 PM
       To: arin-announce at arin dot net
       Cc: nanog at nanog dot org
       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 at arin dot net.  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
      
      
      
      
      
      *             APOPS: Asia Pacific Operations Forum              *
      * To unsubscribe: send "unsubscribe" to apops-request at apnic dot net *