Actually, as whois service is tested prior to delegation, you have to enter the zone with whois not in the TLD in the first place, and then using an IANA change request to move it. ICANN mentioned that the main requirement for standardised whois.nic.<TLD> is CA-related activities, so they will probably don’t mind not having whois.nic.<TLD> prior to the 120-days after contract signing where you cannot delegate anything besides nic.<TLD> Rubens On Nov 20, 2013, at 12:25 PM, Alexander Mayrhofer <alexander.mayrhofer@nic.at> wrote:
I'm using whois.nic.<TLD> - and, yes, nic.<TLD> is properly delegated and reachable in that case, but "whois.nic.<tld>" returns an NXDOMAIN. My understanding is that ICANN requires the WHOIS service to be offered under that hostname... See the respective specification in the AGB..
Indeed, the IANA record shows a different server - so, do i understand correctly that you can actually submit to IANA a different WHOIS server than the one required by ICANN? Can anyone who's already delegated confirm this?
Alex
-----Ursprüngliche Nachricht----- Von: Rubens Kuhl [mailto:rubensk@nic.br] Gesendet: Mittwoch, 20. November 2013 15:02 An: Alexander Mayrhofer Cc: gtld-tech@icann.org Betreff: Re: [gtld-tech] Delegated strings: WHOIS & SLAs...
Are you using whois.nic.<TLD> or the WHOIS server mentioned at http://www.iana.org/whois?q=<TLD> ?
Rubens
On Nov 20, 2013, at 10:53 AM, Alexander Mayrhofer <alexander.mayrhofer@nic.at> wrote:
Looking at some of the recently delegated new gTLDs, i was very surprised
to learn that the WHOIS service is unreachable for some of those TLDs (which makes me wonder how they passed PDT, or why the service degraded since then?). Anyways, since WHOIS is included in the SLA requirements of ICANN, this makes me also wonder when the SLA actually "kicks in", and, whether the SLAs are actually being measured right now by ICANN ...
Any information about this?
Alex