Simple Failover
Edit this page

Did you notice something wrong or unclear, or want to add something more to this page?

You can edit the source text of this page on GitHub (click here to learn how).

After you submit your changes ("pull request"), we will review it and update the page.

Problems updating Microsoft DNS server via WMI

Note: This article is specific to Simple Failover v. 1.x
The issues discussed here do not apply to Simple Failover v. 2.0 and later.

The WMI update method in Simple Failover is available only because there are no other secure ways of updating a remote Microsoft DNS server.

When configured correctly, this update method works fine. But it can be difficult to get the client/server WMI and DCOM security configuration setup correctly for this to work.

Unfortunately we are not WMI / DCOM experts and are not able to assist with specific WMI errors.

If you have to use Microsoft's DNS server and run into problems with WMI updates, we suggest that you check Microsoft's documentation for WMI, DCOM, and MS DNS server - and/or consult with experts in these technologies.

There is a blog article dealing with WMI and DCOM permissions issues here. This article is about Hyper-V, but is deals with the same WMI and DCOM issues that many Simple Failover users have reported.

Otherwise we recommend that you use a DNS server which supports TSIG signed updates, such as BIND or Simple DNS Plus.

Comments

Simple Failover

  • Home
  • Product details

  • Features
  • Sample scenarios
  • Screen shots
  • Compare licenses
  • Download

  • Download
  • Buy

  • Pricing
  • New license
  • Upgrade
  • Support

  • Overview
  • Lost License Key
  • Knowledge Base
  • Online documentation
  • Contact us