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 ]

Wilfried Woeber, UniVie/ACOnet, +43 1 436111 355 woeber at cc.univie.ac.at
Fri Mar 19 00:06:32 CET 1993

> individual nets inside the block... If you really want to put it in the
> database, why not send in an object like:
>
> domain:  204.193.in-addr.arpa
> descr:   blah
> zone-c:  <person>
> nserver: <first server>
> nserver: <second server>
> nserver: ns.ripe.net
> ....
>

I'm really in favour of this approach, because it seems to fit nicely into
the system and we can access the information with tools that need not have
any special knowledge, as Marten pointed out already.

Wilfried.

• 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 ]