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/dns-wg@ripe.net/
in-addr.arpa zone data in RIPE database
- Previous message (by thread): in-addr.arpa zone data in RIPE database
- Next message (by thread): in-addr.arpa zone data in RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Havard Eidnes
Havard.Eidnes at runit.sintef.no
Wed Mar 3 14:36:09 CET 1993
> An indirect way of correcting things via submissions to the RIPE DB in my > view is far from ideal, as it may well introduce unnecessary delays. Soon this argument will be moot for at least 193.in-addr.arpa... > And once you start doing such things for the reverse servers, the next > step may well be doing the same for "forward servers"; then how can e.g. > a top level domain registrar determine whether a given change is valid, > e.g. comes from an authoritative person? Call (ie. phone) the supplied administrative contact person? How do you ensure authority today? - Havard
- Previous message (by thread): in-addr.arpa zone data in RIPE database
- Next message (by thread): in-addr.arpa zone data in RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]