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]/
Domain object template
- Previous message (by thread): Domain object template
- Next message (by thread): Domain object template
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Francis Dupont
Francis.Dupont at inria.fr
Wed Jan 11 14:28:59 CET 1995
In your previous mail you wrote: I have a couple of comments on this draft: > admin-c: The admin-c attribute contains the name or the NIC I suggest to make mandatory that the administrative contact should reside on the site itself. Assume that people have outsourced the 'technical stuff' of their network, then it is likely that the technical contact is someone belonging to another company, and it might be difficult to get in touch with the holder of the domain itself because the address/phone number is different. => the admin contact for domains is different from the admin contact for networks. It is explicitely an administrative person who can answer to questions about name property, legal problems, etc... In fact I understand your problem but I believe the change should be done in the network template. > nserver: The nserver attribute contains the list of > nameservers for of this domain, primary first. The > format is fully qualified domain name without > trailing "." OR IP Address(es) of the nameserver. > Only one server should be described per line. An > example: > > nserver: iraun1.IRA.UKA.DE > > Status: optional, multiple lines allowed Can we please drop the possibility of allowing IP numbers here? If one of the secondaries of your domain changes IP number, then he has the nearly impossible task of finding all these outdated references. Bind only allows hostnames here; I think it is a good idea to restrict the database in the same way. => IP numbers were allowed in the previous template then we need a general agreement before dropping this possibility... Also, we might add 'the first nserver listed is the primary for the zone' => "primary first" is in the text. > dom-net: The dom-net attribute contains the list of IP net- Can someone please explain why it is useful to record this? Seems that this info might get outdated quickly as it isn't related to the domain _name_. => there is a loose binding between names and addresses. This attribute can be used if someone'd like to describe it. This attribute has been made optional then you use it only if you like. Regards Francis.Dupont at inria.fr
- Previous message (by thread): Domain object template
- Next message (by thread): Domain object template
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]