-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New generic gTLDs #10
Comments
When looking to the reality, not all of the new gTLDs have whois.nic.TLD syntax, lots (to not even say most) of them are whois.sponsorname.TLD or whois.registryname.TLD. So we will have to maintain a list of WHOIS servers further on, I guess. On the other hand, I do not believe to a "another thousand" for this year, the roll out has happened much much slower compared to the aggressive marketing out there. |
Pull request #17 should cover this issue for now and proofs that it's unfortunately not only "whois.nic.TLD". |
The standard Registry Agreement for new gTLDs says that registries MUST operate a whois service at whois.nic.tld. If there are any new TLDs which don't, they're in breach of their contracts, and a complaint to ICANN would get them to comply. |
I guess the must after some time, but not immediately? |
From @jodrell:
"As you may know, several hundred new gTLDs have recently been delegated and another thousand will roll out this year. They can easily be supported by changing jwhois to use "whois.nic.TLD" as the server for any unknown generic TLD (ie the last label in the domain matches /^A-Z{2,63}$/i). Is that something that can be expressed in the configuration file syntax or does it require a change to the code?"
The text was updated successfully, but these errors were encountered: