Configuring DNS for HCP

Installing an HCP RAIN System - Final On-Site Setup

File Size
35463 KB
Part Number

Domain name system (DNS) is a network service that translates or resolves domain names (for example, into IP addresses for client access. The service is provided by one or more servers, called name servers, that share responsibility for resolving client requests.

An HCP system can exist as multiple domains in the DNS — one for each front-end network defined in the system. Each of these domains must be a subdomain of a DNS domain to which you have administrative access, such as your corporate domain. All nodes that have IP addresses defined for a given front-end network belong to the HCP domain defined for that network.

Note: If you enable the management network, you cannot access your front-end network through DNS unless you create secondary zones for the management network.

To enable access to HCP by domain name on any given network, you need to configure the HCP domain for that network in your DNS. You can use either secondary zones or stub zones.

Following is the workflow for this chapter:

  • A discussion on the advantages of using DNS
  • A description of zones, secondary zones, and stub zones
  • The instructions for verifying the HCP domain definitions
  • DNS considerations for implementing HCP service by remote systems

For information about domains defined in HCP, see About Domains. For information about HCP networks, see About virtual networking with HCP.

Note: HCP does not require DNS. For information about using HCP without DNS, see System Management console URL. When communicating with a DNS server, HCP may send packets that are larger than 512 bytes. Ensure that these packets can pass through your corporate firewall.