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/db-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 ]
Antonio_Blasco Bonito
bonito at nis.garr.it
Tue Mar 2 13:00:57 CET 1993
> > Questions: > Should we automatically make the suggested changes in the > RIPE database? > No. I agree because there could be some cases which are not properly detected by the automated scripts or other cases where a dns-manager is voluntarily keeping things disalligned > > Or should we send mail to the technical contacts asking them > to change things? > Yes. I agree because many dns-managers do not even know of their registration problems. > > We have asked the NIC accept change notices from us, so that > registration of reverse servers in the database would be > enough to get them into the DNS. Is this desirable? > NO!! I do not agree, I think it would be very useful to the European networking community to interact with RIPE-NCC only instead of having to interact with both RIPE-NCC and the US NIC I don't see the point in what Piet says: > > These actions would bring RIPE on the edge of interfering > with the responsabilities of the authoritative persons for > a given zone, be it for "forward" or reverse mapping. The > best RIPE can do is to send a notification to the authority > of a given zone in case of obvious *errors*, NOT if servers > are missing in the DB, since there may be good reason why > they are "missing". Suppose I would be in foo.XX and I would > have a large network with, say, 10 internal and 2 external > nameservers for my domain; if I would loose connectivity to > the outside world, those 10 internal nameservers would be > unreachable and it would be pointless to have nameservers > all over the Internet try to query them all. Therefore I > would have only, say, 2 internal and the 2 external servers > listed for foo.XX in the XX zone file and in the RIPE DB > and I would absolutely not appreciate it if RIPE would send > me time and again a notification that there are more servers > for foo.XX than actually listed in the XX zone or the DB. If you "have only, say, 2 internal and the 2 external servers listed for foo.XX in the XX zone file" how could the RIPE-NCC script discover the other 8 internal servers? Looking in glass ball? ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito at 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 ---------- ----------
- 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 ]
[ db-wg Archives ]