The Domain object *is* a burden. All the information that is really important already is in the DNS. That's why the domain object at european level is never updated. Drop this thing PLEEEAAASEEE. Thanks for your support, Jose. However, I want to be more precise: the Domain object *in the RIPE database* is a burden and should be dropped. A domain "entity" as such is not only useful, but by its very nature is something that is already well-maintained and therefore very up-to-date: by the top level domain registrar. Direct 'whois' access to that information is and stays useful, because not *everything* is in DNS; it can't even be without overloading [cache/memory] of nameservers and hosts all 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 located where the top level domain itself is administered can serve more purposes, like immediately notifying the maintainer of any inconsistencies between the administration and the top level zone file. Piet

.... 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