About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: in-addr.arpa zone data in RIPE database

  • To: (Daniel Karrenberg)
  • From: (Antonio_Blasco Bonito)
  • Date: Wed, 3 Mar 93 13:13:52 MET
  • Cc:
  • Organization: GARR Network Information Service

Daniel Karrenberg says:
> What remains open is the question on whether in-addr.arpa zone
> registrations should be effected automatically by registering the
> 'rev-srv' field in the RIPE database. I have had quite a few
> comments from people who want this and I personally agree it would be a
> nice feature.  Some people actually assumed this was the way it was working
> already and complained that they had to register in-addr.arpa separately
> with the NIC! 
> 
> I do not see Piet's argument that this would mean a loss of authority of
> the network contacts.  They have the same authority for changing the
> RIPE database than they have for changing the NIC database which then
> generates the in-addr.arpa zone information.  Just the procedure would
> be different, and easier: One stop shopping with no additional cost
> (and no warranty of agency :-), sorry inside joke).
> 
> So my proposal would be to do this in steps:
> 
> First clean up the inconsistencies in the RIPE database using the
> procedure above. 
> 
> Then populate the database with the current in-addr.arpa information,
> notifying the tech contacts of each change.
> 
> After these two steps the information in in-addr.arpa and both the NIC
> and RIPE databases is consistent. 
> 
> Then initiate changes of in-addr.arpa whenever the 'rev-srv' attribute
> in the RIPE DB is changed.  This means the one stop shopping is
> effective.  Until confidence is built we can notify the tech contacts 
> whenever such a change is made. 
> 
> Is this acceptable? 

YES, I very much agree with this plan.

I have to say, commenting some other mail on the subject, that the
DNS is a distributed database BUT the in-addr.arpa registration is
indeed a centralized service, so I prefer very much to have the
RIPE-NCC as my counterpart in this tedious matter, rather than the
US NIC. The NCC has proven to much more efficient and responsive
than the US NIC. Full stop.

----------                                                     ----------
Antonio_Blasco Bonito                          E-Mail: bonito@localhost
GARR - Network Information Service      c=it;a=garr;p=garr;o=nis;s=bonito
c/o CNUCE - Istituto del CNR                         Tel: +39 (50) 593246
Via S. Maria, 36                                    Telex: 500371 CNUCE I
56126 PISA   Italy                                   Fax: +39 (50) 904052
----------                                                     ----------



  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community