Hal9000 Posted June 2, 2017 Share Posted June 2, 2017 Hi there, I noticed in my activity log that there are messages like this: WHOIS Lookup Error for 'blablabla.store': error detail unknown While .design is contained in the dist.whois.json, I added .store myself in whois.json [ { "extensions": ".shop", "uri": "socket://whois.nic.shop", "available": "DOMAIN NOT FOUND" }, { "extensions": ".store", "uri": "socket://whois.centralnic.com", "available": "DOMAIN NOT FOUND" } ] Which looks correct to me. Either way, the "error detail unknown" is not very helpful... what could be wrong? 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted June 2, 2017 Share Posted June 2, 2017 .store is correct and working... .shop should be... { "extensions": ".shop", "uri": "socket://whois.nic.shop", "available": "queried object does not exist" }, with regards to the error, that usually means that your server IP has been marked by CentralNic as an untrusted source (usually for making too many whois searches through their whois server) - if you contact CentralNic support, they should be able to reset that for you. https://forum.whmcs.com/showthread.php?86494-New-gTLDs-Whois-Server&p=518326#post518326 0 Quote Link to comment Share on other sites More sharing options...
Hal9000 Posted June 2, 2017 Author Share Posted June 2, 2017 Thanks. Found out that whois.nic.store also works. [ { "extensions": ".shop", "uri": "socket://whois.nic.shop", "available": "queried object does not exist" }, { "extensions": ".store", "uri": "socket://whois.nic.store", "available": "DOMAIN NOT FOUND" } ] 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted June 2, 2017 Share Posted June 2, 2017 Thanks.Found out that whois.nic.store also works. it's will do as it's just an alias to whois.centralnic.com - btw, .design is another CentralNic TLD too. 0 Quote Link to comment Share on other sites More sharing options...
Hal9000 Posted June 2, 2017 Author Share Posted June 2, 2017 Somehow centralnic is reeeally slow in replying, often resulting in timeout errors in WHMCS. WHOIS Lookup Error for 'foo.store': Error: 110 - Connection timed out I can do a whois in the server shell, it takes over 20 seconds until a reply comes in... So I guess I will contact CentralNic support anyway, maybe they throttle my IP or something... 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted June 2, 2017 Share Posted June 2, 2017 it's happened to us a few times - CentralNic don't really want you using whois to check domain availability, but with WHMCS there isn't an alternative - unless you have a lookup provider that offer these TLDs. "Connection Timed Out" is a sure-fire certainly that the IP is being blocked. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.