This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
193.in-addr.arpa block delegation procedures (draft)
- Previous message (by thread): 193.in-addr.arpa block delegation procedures (draft)
- Next message (by thread): 193.in-addr.arpa block delegation procedures (draft)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Antonio_Blasco Bonito
bonito at nis.garr.it
Wed Mar 17 11:23:58 CET 1993
> > Please read the paper below and comment within one week. We will finalize > > this paper next week, and then start delegating blocks of Cs in the domain. > > The paper looks just fine. My only comment is that perhaps there are a few > things left unsaid? Anyway, I am left with the following questions: > > - how do one request delegation of a subdomain of 193.in-addr.arpa. > Contact hostmaster at ripe.net with a free-form text message, or should we > bother to create a form? > > - How will the domain administrators for the subdomains of 193.in-addr.arpa > be made aware of a desire to have delegation installed for a subdomain? > There was some talk about doing this semi-automatically with the nic when > a RIPE network registration form was sent in to ripe-dbm at ripe.net or > assign at ripe.net, could this be used here (in addition to other means)? > > Regards, > > - H}vard I had the same questions in my mind while reading the paper. I have thought some answers: 2a. The names of the reverse nameserver which are delegated by RIPE-NCC to act as authoritative servers for a 256-class C block are sent to the RIPE-NCC and registered in the RIPE db using a template like this: inetnum: 193.x.0.0 (where x is the block number) <administravia> zone-c: <person> rev-srv: <first server name> rev-srv: <second server name> rev-srv: ns.ripe.net as soon as the Local IR receives from RIPE-NCC a new block to administer. 7. Usually the registration of reverse servers for individual class C nets or class C subblocks is done by the service provider who is administering the whole 256-class C block who in turn notifies the RIPE-NCC sending an updated network template for inclusion in the RIPE db. However should the RIPE-NCC receive any template for a single class C net or subblock not from the service provider, they must forward the template to the authoritative zone-c for the 256-class C block. Please note that I am using the zone-c tag in a network template: this is presently not allowed by the RIPE db rules, but I think we need to precisely qualify this kind of contact information. ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito at nis.garr.it 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 ---------- ----------
- Previous message (by thread): 193.in-addr.arpa block delegation procedures (draft)
- Next message (by thread): 193.in-addr.arpa block delegation procedures (draft)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]