caisc Posted February 12, 2017 Share Posted February 12, 2017 (edited) Hi, I noticed that on my Admin end Activity Log is having following entries - Activity Log - --------------------- System WHOIS Lookup Error for 'myresellerdomain.xyz': error detail unknown 47.8.2.7 58 minutes ago System WHOIS Lookup Error for 'myresellerdomain.in.net': extension not listed in /resources/domains/dist.whois.json or /resources/domains/whois.json 47.8.2.7 58 minutes ago System WHOIS Lookup Error for 'myresellerdomain.ind.in': extension not listed in /resources/domains/dist.whois.json or /resources/domains/whois.json 47.8.2.7 58 minutes ago System WHOIS Lookup Error for 'myresellerdomain.firm.in': extension not listed in /resources/domains/dist.whois.json or /resources/domains/whois.json 47.8.2.7 Right now I am using Standard WHOIS as Lookup Provider How do i fix these WHOIS Lookup Errors, because client will think that domain is not available while it might be available. Thanks Edited February 12, 2017 by caisc 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 12, 2017 Share Posted February 12, 2017 http://docs.whmcs.com/WHOIS_Servers you'll need to create a whois.json for the TLDs that are missing - going from the above log, there's only 2 to add (ind.in and firm.in) - settings will be the same as the other Indian TLDs in dist.whois.json. i'm assuming in.net is a typo by you and should be net.in - which is already in the default whois file. 0 Quote Link to comment Share on other sites More sharing options...
caisc Posted February 13, 2017 Author Share Posted February 13, 2017 Hello brian!, .in.net is not a typo, Resellerclub sells this extension see - https://india.resellerclub.com/domain-reseller/pricing Second issue, when searching for domain with extension .xyz and .in.net WHMCS always shows unavailable no matter what domain i search. screenshot - https://s10.postimg.org/6x2y2qpnt/doman_not_available.png I also created a custom whois.json file located at /resources/domains/whois.json file content - [ { "extensions": ".firm.in,.ind.in", "uri": "socket://whois.inregistry.in", "available": "NOT FOUND" }, ] But after this also WHMCS is showing all .firm.in and .ind.in domains unavailable Thanks 0 Quote Link to comment Share on other sites More sharing options...
caisc Posted February 13, 2017 Author Share Posted February 13, 2017 This looks like a bug - on this page of whmcs - https://www.whmcssetup.com/cart.php?a=add&domain=register Step 1 ------- Try to search domain - tecscscsdfdfdtdocdcmain23.com it will show available and in suggested domains it will show - tecscscsdfdfdtdocdcmain23.firm.in - available tecscscsdfdfdtdocdcmain23.ind.in - available screenshot - https://s23.postimg.org/rea7ka4pn/step1.png Step 2 ------- Now on same page search domain - tecscscsdfdfdtdocdcmain23.firm.in it will show not-available brian! plz check 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 13, 2017 Share Posted February 13, 2017 Hi, .in.net is not a typo, Resellerclub sells this extension see - https://india.resellerclub.com/domain-reseller/pricing apologies, you're absolutely correct - it's one of those CentralNic 3rd-level (subdomain) TLDs. for those using v6 or before... .in.net|whois.centralnic.com|DOMAIN NOT FOUND for v7... { "extensions": ".in.net", "uri": "socket://whois.centralnic.com", "available": "DOMAIN NOT FOUND" }, Second issue, when searching for domain with extension .xyz and .in.net WHMCS always shows unavailable no matter what domain i search.screenshot - https://s10.postimg.org/6x2y2qpnt/doman_not_available.png when I do the same on our v7 dev, I see this... I don't think it's a coincidence that .xyz is also a CentralNic domain - so it's possible your server IP has been blocked (marked as 'untrusted' by CentralNic) for using too many whois lookups... https://forums.whmcs.com/showthread.php?86494-New-gTLDs-Whois-Server&p=463651#post463651 if so, you may need to contact CentralNic support and get them to unblock your server IP.... ironically, you wouldn't hit those limits using the resellerclub lookup. I also created a custom whois.json file located at /resources/domains/whois.json the content is correct - except in the whois.json file format, the final entry doesn't have a closing comma.. [ { "extensions": ".firm.in,.ind.in", "uri": "socket://whois.inregistry.in", "available": "NOT FOUND" } ] if you add any entries for different TLDs before this, then you can add the comma at the end of them... if you add any entries after these two, then remember to add a comma to the end of the above entry. But after this also WHMCS is showing all .firm.in and .ind.in domains unavailable hopefully updating your whois.json to the above will fix that. This looks like a bug - brian! plz check it will likely be because your whois entries were wrong... correct that and see if the issue still occurs. 0 Quote Link to comment Share on other sites More sharing options...
caisc Posted February 13, 2017 Author Share Posted February 13, 2017 (edited) Hi, I have updated my whois.json file located at /resources/domains/whois.json as below - [ { "extensions": ".in.net", "uri": "socket://whois.centralnic.com", "available": "DOMAIN NOT FOUND" }, { "extensions": ".firm.in,.ind.in", "uri": "socket://whois.inregistry.in", "available": "NOT FOUND" } ] This fixed issues for .firm.in and ind.in domain But for some reason problem is still there for .in.net and .xyz extension, see screenshot - https://s31.postimg.org/7wo2kzxgb/xyz_issue.png For .in.net I have created entry in whois.json file as you can see above For .xyz there is already entry in dist.whois.json by default as - { "extensions": ".xyz", "uri": "socket://whois.nic.xyz", "available": "DOMAIN NOT FOUND" }, Activity Logs shows - System WHOIS Lookup Error for 'testmy2017domainfebok.xyz': error detail unknown 3 minutes ago System WHOIS Lookup Error for 'testmy2017domainfebok.in.net': error detail unknown brian! as you mentioned - I don't think it's a coincidence that .xyz is also a CentralNic domain - so it's possible your server IP has been blocked (marked as 'untrusted' by CentralNic) for using too many whois lookups... Working on that front, will update shortly. Edited February 13, 2017 by caisc 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 13, 2017 Share Posted February 13, 2017 But for some reason problem is still there for .in.net and .xyz extension,see screenshot - https://s31.postimg.org/7wo2kzxgb/xyz_issue.png For .in.net I have created entry in whois.json file as you can see above For .xyz there is already entry in dist.whois.json by default as - Now what next read what I posted previously - your server IP is likely being blocked by CentralNic... it's their whois server you're trying to access and if you do it too often, they block the IP. I can think of two simple ways to test this... 1. add some other CentralNic tlds to your pricing (e,g online, .site, .ink) - they're already in dist.whois.json and so should work out of the box... my guess is that they'll all be unavailable too. 2. go to the Softaculous WHMCS Demo and do a search for any .xyz domain (i've just added .xyz to its domain pricing). the Softaculous WHMCS demo should be a clean install of v7.1.1 - so if a .xyz TLD search works on their site (as I think it will), but not yours, then either should confirm your IP is being blocked by CentralNic. if that's the case, then the only solution (if you want to use standard whois) will be to contact CentralNic - there's no other way around it. 0 Quote Link to comment Share on other sites More sharing options...
caisc Posted February 13, 2017 Author Share Posted February 13, 2017 brian! can you please confirm the correct place to contact CentralNic team I think its - https://www.centralnic.com/contact/getintouch plz confirm 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 13, 2017 Share Posted February 13, 2017 yeah or just email info@ - when it happened to us, I just opened a support ticket with them (we're resellers for them), but you'll have to go through the public route of either filling the contact form or sending an email. 0 Quote Link to comment Share on other sites More sharing options...
caisc Posted February 13, 2017 Author Share Posted February 13, 2017 CentralNic Support was kind enough to unblock our IP within an hour, now everything is working fine. Thanks brian! for pointing in the right direction 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.