I agree completely.
I think Blasco has a point there and will implement this unless someone cries "stop". for MX-only domains both name server and zone contact attributes are actually attributes of the parent (or an ancestor) domain.
Cheers, Ruediger
Daniel
------- Forwarded Message
Date: Fri, 19 Feb 93 18:49:25 MET From: bonito@nis.garr.it (Antonio_Blasco Bonito) To: ripe-dbm@ripe.net cc: staff@nis.garr.it Subject: zone-c tag
Hello NCC people,
I think the update procedure is not right giving the following error:
domain: fis.uniurb.it descr: Universita' degli Studi di Urbino descr: Istituto di Fisica remarks: It is a public institution devoted to researches in some field s remarks: of Physics and Biomedical Engineering and teaching admin-c: Filippo Martelli tech-c: Flavio Vetrano tech-c: Pietro Dominici remarks: MX-only source: RIPE changed: domain@nis.garr.it 930217 WARNING: mandatory attribute "zone-c" missing in object
A MX-only domain has no nameserver and therefore cannot have a zone-c contact information. I think that zone-c should not be considered a mandatory attribute.
All my best. - ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito@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 - ---------- ----------
------- End of Forwarded Message
Ruediger Volk Universitaet Dortmund, Informatik IRB DE-NIC Postfach 500 500 D-W-4600 Dortmund 50 Germany E-Mail: rv@Informatik.Uni-Dortmund.DE Phone: +49 231 755 4760 Fax: +49 231 755 2386
I agree completely. > I think Blasco has a point there and will implement this > unless someone cries "stop". for MX-only domains both name server and zone contact attributes are actually attributes of the parent (or an ancestor) domain. Agreed. This has been the case since ages for MX-only domains under .NL. Piet
I agree completely.
> I think Blasco has a point there and will implement this > unless someone cries "stop".
for MX-only domains both name server and zone contact attributes are actually attributes of the parent (or an ancestor) domain.
Agreed. This has been the case since ages for MX-only domains under .NL.
Piet
Sorry, but I do not fully understand what you mean. I see two altenative possibilities: 1- the zone-c tag refers to the technicians who runs the nameserver of a "fully-managed" or "delegated to" domain. In this case it is to be considered an optional tag for "MX-only" domains. 2- the zone-c tag refers to the technician who runs the nameserver where the MX record of a "MX-only" domain is actually registered. In this case the above needs to be properly stated in the RIPE domain template instructions and zone-c should remain mandatory. I prefer solution 1 but also 2 is reasonable ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito@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 ---------- ----------
for MX-only domains both name server and zone contact attributes are actually attributes of the parent (or an ancestor) domain. Agreed. This has been the case since ages for MX-only domains under .NL. Sorry, but I do not fully understand what you mean. I see two altenative possibilities: 1- the zone-c tag refers to the technicians who runs the nameserver of a "fully-managed" or "delegated to" domain. In this case it is to be considered an optional tag for "MX-only" domains. 2- the zone-c tag refers to the technician who runs the nameserver where the MX record of a "MX-only" domain is actually registered. In this case the above needs to be properly stated in the RIPE domain template instructions and zone-c should remain mandatory. I fail to see the difference. If there is no nameserver for the MX-only domain, the next higher nameserver takes that place and lists the MX RR's and becomes responsible for them. Piet
participants (3)
-
bonito＠nis.garr.it -
Piet Beertema -
rv＠deins.informatik.uni-dortmund.de