Configure the VA Through Configuration Mode
Configuring the VA involves configuring the name, IP details, and local DNS servers. It is mandatory to configure the name and IP, netmask, and gateway (unless already configured). Failing to do this results in the VA not being able to register to Secure Access.
In addition to an IPv4 address, you can also configure the VA with an IPv6 address. Endpoints with an IPv6 address can use the VA for DNS resolution, and Secure Access logs the internal IPv6 address of the endpoint in the reports.
|
Active Directory integration is currently not supported for IPv6 endpoints. |
| Field | Description | ||
|---|---|---|---|
| Name* |
The name associated with the VA in Secure Access. This is a descriptive name, similar to a hostname for a computer or server. If you have multiple hypervisor hosts, appending or prepending numbers or letters to indicate the local hypervisor host is advised.
|
||
| IP, Netmask, and Gateway* |
Give the VA a local, static IP address on the same network as your endpoints which will utilize the VAs for DNS resolution.
|
||
| Local DNS 1-6 | Configure your local DNS servers that will receive DNS queries for internal domains. These are usually your Windows Servers with the DNS server role installed. You can enter IPv4 and/or IPv6 addresses here. For more information and commands to configure local DNS servers, see Local DNS Forwarding. |
*Mandatory parameters for the VA.
If you have entered the Configuration Mode over SSH, to validate status, enter:
config va status
If tests complete without error, the next step is to verify that the VA syncs with Secure Access.