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 ]
Piet Beertema
Piet.Beertema at cwi.nl
Fri Jan 20 12:51:11 CET 1995
.... 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. Commenting here from a RIPE database implementers' point of view, this can be done. Good. Actually I didn't expect otherwise. Again, as with most changes to the software this will take time. Hours? ;-) And general concensus of course..... It's the folks involved with the DNS objects that need to push this, not the NCC. True. Although I'd say it's in the interest of the NCC too to keep the whois service running, or the current service will simply die as far as information about domains is concerned. Piet
- Previous message (by thread): DNS TF meeting
- Next message (by thread): DNS TF meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]