Article ID: 3628, created on Feb 8, 2008, last review on May 11, 2014

  • Applies to:
  • Helm 3

Resolution

Problem
 
When adding or deleting a domain in Helm it fails, and an error appears in the Helm error logs. There are two types of common error you may come across regarding HTTP communication. Both mean that the control server is unable to communicate with the SimpleDNS service, but for slightly different reasons.
 
Error 1
 
2003-05-10 14:15:32 HELMInterfaces:SimpleDNS::ReadZoneFileData Error communicating through HTTP to 'SERVER'(SERVER-IP:8053) (Method '~' of object '~' failed)
2003-05-10 14:15:32 HELMInterfaces:SimpleDNS::ReadZoneFileData Error communicating through HTTP to 'SERVER'(SERVER-IP:8053) (Method '~' of object '~' failed)
2003-05-10 14:15:33 DNS.IDNS_RemoveZone Error communicating through HTTP to 'SERVER'(SERVER-IP:8053) (Method '~' of object '~' failed)
2003-05-10 14:15:33 CDomain.DeleteDomainEx Error communicating through HTTP to 'SERVER'(SERVER-IP:8053) (Method '~' of object '~' failed)
 
Error 2
 
2005-03-23 15:00:49 DNS.IDNS_RemoveZone Error communicating through HTTP to 'SERVER'(SERVER-IP:8053) (The download of the specified resource has failed.)
2005-03-23 15:00:49 CDomain.DeleteDomainEx Error communicating through HTTP to 'SERVER'(SERVER-IP:8053) (The download of the specified resource has failed.)

 
Solution

Before you try anything else, make sure that you can access the Status page of the Simple DNS service; if you can't do this, it means Helm will not be able to either. To check this, simply type the IP and port of your Simple DNS server into a browser, followed by /status - so if you installed Simple DNS on 60.70.80.90 you should type:
 
 
and this should bring up the Simple DNS Status page. If it doesn't, check the following and rectify as appropriate (any of these could be the cause of Error 1):
 
1.) The IP address specified to communicate with the SimpleDNS service is incorrect or is failing.

2.) The SimpleDNS service is not running or has crashed (check this in Windows Services).

3.) The ACL list in the SimpleDNS configuration file does not contain the IP address that the control server is communicating from. (check the Simple DNS Configuration Guide on the WebHost Automation site for further details).

4.) MS XML 4 hasn't been installed on the server. You can tell this is the case because you can access the SimpleDNS service through the web browser on the server, but Helm still has problems.
 
The cause of Error 2 is usually related specifically to point 3.) above. For instance, if you have Helm on a server (e.g. 60.70.80.90) and Simple DNS on a different server, then in the sdnsplus.ini file on the Simple DNS server, the HTTPACL line should read:
 
HTTPACL=127.0.0.1 60.70.80.90
This effectively gives access to the Helm server to communicate with the DNS server.
 
-------
 
If you still have issues after following the above steps, contact your support provider.

152090ff5e9a05ea7e1cf0c248449638 110556ad4b9f1c73a3682661cd1dca89 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF