Skip to main content
Hitachi Vantara Knowledge

Configuring DNS for HCP

Domain name system (DNS) is a network service that translates, or resolves, domain names (for example, example.com) 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 domain 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.

NoteIf 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. To do this, you can use either secondary zones (also called slave zones) or stub zones.

This chapter contains:

  • A discussion of the advantages of using DNS
  • A description of zones, secondary zones, and stub zones
  • Windows and Unix instructions for configuring HCP domains in the DNS
  • Instructions for verifying the HCP domain definitions
  • DNS considerations for implementing HCP service by remote systems
Note
  • HCP does not require DNS.
  • When communicating with a DNS server, HCP may send packets that are larger than 512 bytes. You must make sure these packets can pass through your corporate firewall.

 

  • Was this article helpful?