VAST Cluster supports a single instance of the DNS service. The DNS server listens for DNS requests on port 53 and runs on a dedicated virtual IP (DNS VIP).
To use the DNS service, you need to configure it and enable the service on the VMS via the VAST Web UI or VAST CLI. Before you begin, read DNS-Based Load Balancing.
From the left navigation menu, select Network Access and then DNS.
In the Add DNS dialog, complete the fields:
Enter a name for the DNS server configuration.
For example: vast-dns
Enter a virtual IP to assign to the DNS service. DNS requests from your external DNS server must be delegated to this IP.
For example: 192.0.2.0
If the external DNS server doesn't reside on the same subnet as the DNS VIP, enter the IP of a gateway through which to connect to the DNS server. The gateway IP must be on same subnet as the DNS VIP and reachable from the management network.
For example: 188.8.131.52
Specify a domain suffix. Requests for the specified domain suffix are resolved to the VIPs configured on the cluster.
If domain names are configured per VIP pool, the domain suffix is appended to those domain names to form a valid FQDN for DNS requests to target.
For example: mycorp.cluster.com
VIP Subnet CIDR
The subnet, in CIDR format, on which the DNS VIP resides.
For example, the subnet mask 255.255.0.0 is expressed as 16 in CIDR notation.
If your external DNS server is only exposed to a specific VLAN, you can enter the VLAN here to enable communication with the DNS server. Ensure that VLAN tagging is configured on the MGMT network to which the CNodes are connected. This configuration is not supported through VMS.
This VLAN tag is not related to VLAN tagging per VIP pool.
Valid range: 1 to 4094
If you want to immediately enable the DNS service, turn on the Enabled setting.
The DNS server configuration is created and appears on the DNS tab.
To configure the DNS server from the CLI, use the dns create command.
vcli: admin> dns create --name vast_dns --vip 192.0.2.0 --domain-suffix vastdata.ourcorp.com --vip-gateway 184.108.40.206--enable --vip-subnet-cidr 16