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]/
RIPE DB domain object
- Previous message (by thread): BIND status
- Next message (by thread): RIPE DB domain object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Francis Dupont
Francis.Dupont at inria.fr
Fri May 13 16:43:35 CEST 1994
Here are proposals about the RIPE DB domain object definition Francis.Dupont at inria.fr Some mandatory entries should become optional (i.e. can be missing): - zone-c (zone contact(s)) when the domain is not a zone (technically: it has no SOA RR), for instance MX only domains have no zone contacts. - nserver (name servers) is in the same case - sub-dom (sub domain(s)) when there is no sub domains Some important entries should be redefined: - nserver (name servers): the new syntax should be: (*) name [ (address)+ ] with a star for unpublished (secondary) name servers, fully qualified domain name of the name server and the list of the IP addresses of the name server. We have to write a detailed description of this, for instance what are the mandatory fields, what are unpublished ns, ... - sub-dom (sub domains): this entry should be either not present or not empty. Domain names should be fully qualified (change). New entries like the "notify" entry must be added (it is in the scope of of RIPE DB WG but we have to produce an up to date document about domain object)
- Previous message (by thread): BIND status
- Next message (by thread): RIPE DB domain object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]