Search Engine: Elastic

Article ID: 3928, created on Feb 8, 2008, last review on May 10, 2014

  • Applies to:
  • Helm 4



When adding a domain to Helm, it fails and I get the following in the error log:

The Microsoft DNS Server (SERVERNAME) is currently unavailable.

If you turn on debugging, you will see that dnscmd.exe is not able to create the domain on the remote machine.

You can test this by going to a command prompt and typing

"C:\Program Files\WebHost Automation\Helm\System\dnscmd.exe" REMOTESERVERNAME /ZoneAdd /Secondary REMOTESERVERIP /file

where REMOTESERVERNAME is the NetBIOS name of your remote server, and REMOTESERVERIP is the IP of your remote server.

If the RPC service on the remote machine is disabled, you will get this error:

Command failed:  RPC_S_SERVER_UNAVAILABLE       1722 (000006ba)

This is usually caused by a Windows update which disables the RPC for MS DNS on the machine, meaning that you cannot connect to that machine and create DNS files.


Login to the remote machine then:

1. On the start menu click 'Run' and then type 'Regedit' and then press enter.

2. Navigate to the following registry location:

3. Select Registry Key RpcProtocol and changed it from 4 to FFFFFF.

4. Restart the DNS Service

This should fix the issue.

0331e0e4efc12686c3f22fc2cdda9f03 152090ff5e9a05ea7e1cf0c248449638 3ef1f5f998c0dc182718a7fe4376f875

Email subscription for changes to this article
Save as PDF