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]/
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 ]
Piet.Beertema at mcsun.EU.net
Piet.Beertema at mcsun.EU.net
Tue Mar 2 13:12:05 CET 1993
> > We have asked the NIC accept change notices from us, so tha t > 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 Interaction is fine. But RIPE stepping into someone else's authority is quite something different! I don't see the point in what Piet says: ..... 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? Reread the original message: it explicitly contained a sentence: Then a list of all reverse servers found in the DNS: which implies that DNS is queried to find all (in this case reverse) nameservers. How that's done is irrelevant. Piet
- 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 ]