DNS advantages

Installing an HCP RAIN System - Final On-Site Setup

Version
9.7.x
File Size
35463 KB
Audience
anonymous
Part Number
MK-98ARC016-35

Using DNS provides several advantages over using IP addresses for access to the HCP system. For example:

  • When you use a domain name for namespace access, the HCP DNS manager, which runs on all storage nodes, is responsible for distributing client requests among those nodes. If you use IP addresses, you are responsible for ensuring that the processing load is balanced across the HCP nodes.
  • If an application uses a domain name for access to the HCP system and you change the IP addresses of the HCP nodes, you don’t need to change the application. If the application uses IP addresses and you change the node IP addresses, you need to update the application to specify the new IP addresses.
  • If both IPv4 and IPv6 addresses are defined for a front-end network, applications can use the domain name associated with that network to access the HCP system from client computers that have IPv4 addresses and from client computers that have IPv6 addresses. If an application uses IP addresses to access the HCP system over a front-end network with multiple IP addresses defined for each node, you need to configure the application to access the HCP system using only the IP addresses that are routable from the client computer on which the application is running.
  • If you use a domain name to identify the other system when you create a replication link and the IP addresses for that domain are changed on that system, replication continues without interruption. If you use IP addresses to identify the system and the IP addresses for the system change, replication stops until you change the IP addresses in the relication link.
  • If you use domain names to identify the systems in a replication topology and you enable DNS failover on those systems, client requests can be automatically redirected to other systems in the topology if the target system fails. If you use IP addresses to identify a system in a replication topology and that system fails, client requests targeting that system cannot be automatically redirected to other systems.