HCP System Management Help
When you configure a secondary zone or stub zone for an HCP system, you specify a domain name and the IP addresses of the master name servers for the applicable HCP domain. This causes client requests that identify the system by that domain name to be forwarded to those master name servers.
Namespaces can be configured to accept client requests on HCP systems other than the system targeted by the request when that system is unavailable. To enable this redirection to occur automatically for a namespace:
•DNS failover must have been enabled on the target system.
•The applicable replication link must be failed over. The applicable replication link is the link between the target system and the system to which requests should be redirected.
•The applicable secondary zone or stub zone for the target system must include the IP addresses of the applicable master name servers for the system to which requests should be redirected, where:
oThe applicable secondary zone or stub zone on the target system is the one defined for the data network for the tenant that owns the namespace
oThe applicable master name servers for the system to which requests should be redirected are the ones included in the secondary zone or stub zone for the network with the same name as the tenant data network on the target system
For example, suppose:
•The data network for a tenant is the network named net1.
•The system targeted by a client request has master name servers with IPv4 addresses 192.168.210.15, 16, 17, and 18 and with IPv6 addresses 2001:0db8::101, 102, 103, and 104 for net1.
•The system to which requests should be redirected has master name servers with IPv4 addresses 192.168.24.72, 73, 74, and 75 and with IPv6 addresses 2001:0db8::201, 202, 203, and 204 for net1.
In this case, the secondary zone or stub zone for net1 on the target system would have these IP addresses:
192.168.210.15
2001:0db8::101
192.168.210.16
2001:0db8::102
192.168.210.17
2001:0db8::103
192.168.210.18
2001:0db8::104
192.168.24.72
2001:0db8::201
192.168.24.73
2001:0db8::202
192.168.24.74
2001:0db8::203
192.168.24.75
2001:0db8::204
The secondary zone or stub zone for net1 on the system to which requests should be redirected would have these IP addresses:
192.168.24.72
2001:0db8::201
192.168.24.73
2001:0db8::202
192.168.24.74
2001:0db8::203
192.168.24.75
2001:0db8::204
To enable redirection in both directions between two HCP systems that participate in an active/active replication link, the secondary zone or stub zone for each of the systems must include the IP addresses of the master name servers for the other system.
To enable client requests targeted to one system to be serviced by any of the other systems in a replication topology, the secondary zone or stub zone for that system must include the IP addresses of the master name servers for each of the other systems.
For example, suppose a replication topology includes systems A, B, C, and D. For systems B, C, and D to be able to service requests targeted to system A, the secondary zone or stub zone for system A must include the IP addresses of the master name servers for systems B, C, and D. For systems C, D, and A to be able to service requests targeted to system B, the secondary zone or stub zone for system B must include the IP addresses of the master name servers for systems C, D, and A.
For information on replication and DNS failover, see Replicating Tenants and Namespaces. For information on configuring namespaces to accept redirected requests, see Managing a Tenant and Its Namespaces or Managing the Default Tenant and Namespace.
![]() |
Note: If you are not enabling DNS failover on an HCP system, do not include IP addresses for the master name servers for other systems in the secondary zones or stub zones for that system. |
Trademarks and Legal Disclaimer
© 2017 Hitachi Vantara Corporation. All rights reserved.