Setting Up the DNS for HyperScale X Setup

Commvault HyperScale X uses DNS records to communicate with both the CommServe server and clients in your environment. Hence it is important to properly setup the necessary DNS records before setting up the nodes. Also most of the issues faced during setup are caused by DNS misconfiguration.

• DNS records are required for the data protection and the optional 1GbE management network interfaces in each of the nodes. DNS should resolve to the IP addresses associated with each node.

• Configuring DNS entries on multiple redundant DNS servers is recommended for greater resiliency.

• DNS entries are required to be in place for each HyperScale X node, both for the initial setup, and subsequent operations.

• Both forward (A) and reverse (PTR) records are required.

  Note

  DNS entries are only required for the data protection network and the optional 1GbE management network. Storage pool network does not need DNS entries.

• All DNS records must be Fully Qualified Domain Names (FQDN). For example, the name must be HSA1.domain.com; not HSA1.

  Note

  A DNS server is required. Hosts file entries cannot be used as an alternative.

If your DNS server is configured for non-secure DNS updates (not recommended by Microsoft), this should be disabled before attempting the node setup.

Configuring DNS Records

• For detailed information on creating and verifying DNS records,see the Microsoft support site.

• Depending on your network topology, setup the necessary DNS records as described in the Network Requirements section of the following pages:

  • Basic Topology

  • Basic Topology with Management Network

  • Bonded Topology

  • Bonded Topology with Management Network

  • VLAN Topology

  • VLAN Topology with Management Network

  • Bonded VLAN Topology

  • Bonded VLAN Topology wth Management Network

Verifying DNS Entries

Verify and validate the DNS records associated with ALL the nodes that you plan to setup, before deploying the Commvault HyperScale X nodes.

The DNS records can be validated from any computer that has access to the DNS server.

Verifying Forward Records (A Records)

Use the following command to verify A records:

# nslookup <node_fqdn>

Example:

# nslookup HSA1.domain.com
Server:           172.16.10.11
Address:          172.16.10.11#53
Name:     HSA1.domain.com
Address:  172.16.10.101

Verifying Reverse Records (PTR Records)

Use the following command to verify PTR records:

# nslookup <node_IP_addr>

Example:

# nslookup 172.16.10.101
Server:           172.16.10.11
Address:          172.16.10.11#53
101.10.16.273.in-addr.arpa      name =HSA1.domain.com

Related Topic

Troubleshooting Network Configuration Errors