Knowledge Base

Active Directory Integrated Environments

VMware recommends that VMware vCenter Server Heartbeat be installed in an Active Directory Integrated DNS environment.

In a standard DNS zone, there can be one Primary and multiple Secondary DNS servers. The Primary is the Start of Authority (SOA) server for that zone and the other servers are secondary. When adding a new host record, like a new server is added into the zone, the record is inserted only in the Primary DNS server. The information is available on the Secondary servers during the replication process between the Primary and Secondary servers.

In an Active Directory (AD) Integrated DNS environment, all servers are updated within the AD through multi-master replication (a change on any one server is replicated to all other Active Directory databases).

For instructions on converting to an Active Directory Integrated DNS environment, see the Additional Information section.

Non-Active Directory Integrated Environments

VMware recommends that if the current environment is not Active Directory integrated, that migration to Active Directory integrated be performed prior to installing any VMware solution. See the Additional Information section for Microsoft Knowledge Base articles that provide procedures for migrating to an Active Directory integrated environment.

In the event that Active Directory integration is not possible or not desired, the DNSUpdate utility can be configured to update specific DNS servers when identified by IP address.

To update DNS servers using the DNSUpdate utility in a non-Active Directory integrated environment:

1. Launch the VMware vCenter Server Heartbeat Console.
2. Click Advanced > Application.
3. Select Tasks.
4. Click User Accounts.
5. Click Add.
6. Enter the credentials for an account with rights to update the DNS (a member of the Administrators or Server Operators group on the target server).
7. Click OK and Close.
8. Click Add to add a new task.
9. Provide a descriptive name for the Task.
10. Select Network Configuration for Task type.
11. Select either Primary or Secondary for the server the task should run on as appropriate.
12. In the Command field, run the DNSUpdate command with appropriate flags as shown in the example.
13. In the Run As field select the user appropriate user account from the dropdown and click OK.

For example, Dnsupdate -p <Primary IP address> -s <Secondary IP address> -ns <DNS Server IP Address>