Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Using Heartbeat across a WAN with Windows DNS (2030604)

Symptoms

  • When performing a switchover in a WAN configuration, the protected services may fail to start
  • The Public DNS service name fails to update
  • The DNS Servers are running Windows 2008 or later

Cause

Windows 2008 DNS Servers have extra security measures in place that prevent legacy clients from performing updates.

Resolution

To resolve this issue:

  1. Download the updated DNSUpdate package attached to this article:

    • If Heartbeat is running on a 32-bit operating system: DNSUpdate 32-Bit 01.06.02.zip
    • If Heartbeat is running on a 64-bit operating system: DNSUpdate 64-Bit 01.06.02.zip

  2. Extract the files to install_directory\R2\bin.

    Note: By default, this directory is C:\Program Files\VMware\VMware vCenter Server Heartbeat\R2\Bin.

  3. When prompted to overwrite the files, click Yes.


Once the updated DNSUpdate files are in place, follow these steps to ensure DNS update tasks are successful:

  1. Ensure that the DNSUpdate (Primary and Secondary) tasks in the Heartbeat Console are set to run this command:

    "C:\Program Files\VMware\VMware vCenter Server Heartbeat\R2\Bin\dnsconftool.exe" -auto

    Note: This path may vary if Heartbeat was not installed in the default location.

  2. Ensure that both nodes are configured to use Windows DNS Servers in the Network Adapter configuration.

  3. Ensure that the DNSUpdate task is configured to run as a user with full security permissions to update the Windows DNS Server (that is, a user in the Active Directory DnsAdmins group).

  4. As updating the DNS Server requires elevation, turn off Windows UAC on both nodes.

Additional Information

In a WAN configuration, the Heartbeat nodes will each have a unique DNS record that resolves to its Management IP address. The Public DNS service name is what all hosts and clients will use to find the vCenter. This DNS record will resolve to the configured Public IP address of the Active node.

Attachments

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings
Actions
KB: