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]/
DNS TF meeting
- Previous message (by thread): DNS TF meeting
- Next message (by thread): DNS TF meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marten Terpstra
Marten.Terpstra at ripe.net
Fri Jan 20 11:52:54 CET 1995
* over the Internet. The current RIPE 'whois' * access however is well-established, which is * why I've suggested to drop all Domain objects * except for a special one ("*td") for the top * level domains, which would then contain an * attribute ("*ws") pointing to the whois server * for that top level domain. RIPE's whois server * can than act as a "forwarder" for requests for * <domain>.<top_level_domain> (much like DNS!), * thus keeping the current whois service, but * resulting in far more up-to-date and reliable * information. Besided, the whois servers that Commenting here from a RIPE database implementers' point of view, this can be done. The database software will have to be taught how domains work similar to more/less specifics for IP addresses and how to forward queries. Again, as with most changes to the software this will take time. And general concensus of course..... It's the folks involved with the DNS objects that need to push this, not the NCC. -Marten
- Previous message (by thread): DNS TF meeting
- Next message (by thread): DNS TF meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]