HostLANGUR Posted July 18, 2012 Share Posted July 18, 2012 Hi, I am new to the WHMCS forums, i have tried to get help from enom about this, but they say it is to do with WHMCS not them.. When trying to search for a domain in whmcs, it brings up the following error: "There was a problem connecting to the domain registry." My server IPS have been whitelisted with enom because the admin widget to display my balance works fine. Thanks, Dean. 0 Quote Link to comment Share on other sites More sharing options...
Damo Posted July 18, 2012 Share Posted July 18, 2012 Check your firewall for whois ports being closed. 0 Quote Link to comment Share on other sites More sharing options...
HostLANGUR Posted July 18, 2012 Author Share Posted July 18, 2012 Hi, i have tried this and disabled CSF before asking on the forums - but still the error comes up. Very odd indeed.. 0 Quote Link to comment Share on other sites More sharing options...
Damo Posted July 18, 2012 Share Posted July 18, 2012 What about a hardware firewall at your NOC? Are you able to perform a whois lookup from a shell command line on this server? 0 Quote Link to comment Share on other sites More sharing options...
HostLANGUR Posted July 18, 2012 Author Share Posted July 18, 2012 Yeah i'm able to perform whois lookups: root@devil [/etc]# whois whmcs.com [Querying whois.verisign-grs.com] [Redirected to whois.enom.com] [Querying whois.enom.com] [whois.enom.com] =-=-=-= Visit AboutUs.org for more information about whmcs.com <a href="http://www.aboutus.org/whmcs.com">AboutUs: whmcs.com</a> Domain name: whmcs.com Registrant Contact: WHMCS Enom Domains WHMCS Enom Domains () Fax: 13 Avon Drive Bedford, GB MK41 7AE GB Administrative Contact: WHMCS Enom Domains WHMCS Enom Domains (domains@whmcs.com) +44.02081441086 Fax: +44.02081441086 13 Avon Drive Bedford, GB MK41 7AE GB Technical Contact: WHMCS Enom Domains WHMCS Enom Domains (domains@whmcs.com) +44.02081441086 Fax: +44.02081441086 13 Avon Drive Bedford, GB MK41 7AE GB Status: Locked Name Servers: dns1.whmcs.com dns2.whmcs.com Creation date: 10 Jun 2005 10:24:00 Expiration date: 10 Jun 2015 10:24:0 0 Quote Link to comment Share on other sites More sharing options...
HostLANGUR Posted July 18, 2012 Author Share Posted July 18, 2012 An update to this thread: it seems certain domains .com/.net/.name will not connect to enom's registry but yet .info/.org/.us are. And of course enom are refusing all blame that it is anything to do with them. 0 Quote Link to comment Share on other sites More sharing options...
techdruid Posted March 15, 2013 Share Posted March 15, 2013 I recently migrated to a new server (from CentOS 5.8 to 6.4). I changed my IP with eNom. I know that it's working because I modified contact details for a domain within WHMCS and it did update at eNom. However, I am receive this same error as above when attempting to search for domain names (.com/.net/.org). There was a problem connecting to the domain registry. Please try again later. I went as far as to sniff the network traffic on the WHMCS server. I can see that the WHMCS system is contacting my DNS server asking for the root servers. But then there is nothing else after that. The WHMCS is doing nothing on the network after this. Outbound firewall is completely open. I'm not sure where to look for any kind of trace on this problem. I think I'm going to log a ticket with WHMCS since it doesn't seem to be even trying to reach eNom. My guess is that maybe there is some library or something missing from my new server. 0 Quote Link to comment Share on other sites More sharing options...
techdruid Posted March 15, 2013 Share Posted March 15, 2013 Problem solved. After logging a ticket, and being provided with a "whoistest.php" from WHMCS, I received the following error. Beginning WHOIS Lookup Warning: fsockopen(): unable to connect to whois.crsnic.net:43 (Permission denied) in /var/SOMEFOLDER/whoistest.php on line 8 WHOIS Lookup Finished This reminded me that SELINUX is enabled by default on CentOS. After disabling SELINUX, this problem was resolved. Just edit /etc/selinux/config replace enforcing with disabled and reboot. 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.