The VAST Cluster compute load is designed to be balanced across all of the CNodes. VAST Cluster features a DNS server that can handle VIP distribution and simplify DNS administration. The DNS server returns a single VIP per query and is automatically updated of VIP pool changes.
There are several ways to use the DNS server. It is also possible to configure VIP distribution on your external DNS server. There are several advantages to configuring VIP Distribution through the VAST Cluster DNS server.
You can choose to configure DNS-based VIP distribution any of the following ways:
Using VAST Cluster DNS. In which DNS queries for subdomains are forwarded via an external DNS server to a single domain and queries are distributed to specific VIP pools according to subdomains.
Using an external DNS server. In which DNS queries are forwarded by an external DNS server to all VIPs and the client randomly selects a VIP.
In this configuration, the DNS VIP responds to A-record requests for the DNS VIP for each subdomain and distributes those requests among the VIPs in that pool.
To set this up, do all of the following:
-
Decide on:
A domain suffix that will be common to all FQDN(s) that clients will use to request cluster access. For example: cluster.mycorp.com.
One or more short domain names which you can set per IP pool as subdomains. The domain suffix will be appended onto each domain name to form an FQDN.
For example: If domain suffix is cluster.mycorp.com and domain names are domain1, domain2 and domain3, then you will be able to forward requests for domain1.cluster.mycorp.com, domain2.cluster.mycorp.com, and domain3.cluster.mycorp.com each to a different VIP pool. You'll only need one DNS delegation for cluster.mycorp.com which will forward all of the above FQDNs to the VAST DNS server.
Note
You could choose your top level domain name, such as mycorp.com as the domain suffix but that has the disadvantage that you will need to define a separate DNS delegation record for each subdomain.
-
Create a separate VIP pool for each set of VIPs that you want to place in a different domain. See Managing Virtual IP Pools.
Tip
You can also restrict view access to specific VIP pools via the view policy.
-
In each such VIP pool, set the Domain Name to one of the short domain names you chose. If the VIP pools are already defined, modify the VIP pool to add a subdomain name in the Domain Name field.
Note
The VAST Cluster DNS server requires the domain name to be set on the VIP pool(s) even if you do not need more than one subdomain. You can set the domain name to be the same in more than one VIP pool if needed.
Configure the DNS server. Set the domain suffix to be appended to each of the domain names set for the VIP pools.
On the client DNS server, configure a single DNS delegation record. The DNS delegation record should forward any client requests for the domain to the VAST Cluster DNS VIP. For each request for a specific subdomain, the VAST Cluster DNS server will return a VIP from the pool associated with the subdomain.
Example
Suppose:
There are two VIP pools: pool1 and pool2.
In the VIP Pool configuration of pool1, the domain name is set to domain1.
In the VIP Pool configuration of pool2, the domain name is set to domain2.
In the DNS server configuration, the DNS VIP is set to 1.2.3.4, while the Domain Suffix is set to cluster.mycorp.com.
On the client DNS server, a single delegation record forwards all requests for cluster.mycorp.com to the IP 1.2.3.4.
This configuration can:
Resolve domain1.cluster.mycorp.com and return a single VIP from pool1
Resolve domain2.cluster.mycorp.com and return a single from pool2
The VAST Cluster DNS server is an optional configuration. The alternative is to configure all DNS forwarding on an external DNS server. You do this by configuring delegation records to forward client requests for the VAST FQDN to all the VIPs configured on the cluster. In this case, your DNS server responds to each query with all CNode VIPs. The client randomly selects one of the IPs.
If you choose this option, you need to ensure that your DNS server is updated whenever any change is made to the VIP pools on the VAST Cluster.
The following table summarizes the differences between using the VAST Cluster DNS server to distribute the compute load vs using an external DNS server to distribute the load.
VAST Cluster DNS Server |
External DNS Server |
|
|---|---|---|
# IPs returned per DNS query |
One IP. Client does not select IP. |
All IPs. Client selects IP. |
How is the DNS server updated of changes in VIP pool ranges? |
Automatically |
Manually |
Ability to create a single-DNS delegation record as well as separate 'sub-records' for several VIP pools WITHOUT needing to create additional DNS records on the external DNS server? |
Yes |
No |
Comments
0 comments
Article is closed for comments.