You can configure a local DNS virtual service on all the clusters where the DNS service needs to be hosted or bound to the local g-dns SE group.

For each Controller Cluster, configure an SE group to host the DNS virtual service, for example, g-dns. To configure the SE group, navigate to Infrastructure > Cloud > Service Engine Group. For more information on DNS sites, see Binding DNS Virtual Services to GSLB Sites.

Note:

  • The virtual service and SE group names need not be identical across all GSLB sites.

The default value for the Virtual Services per Service Engine field is 10. In the following screenshot, the value is set as 1 as part of recommended practice.



In Santa Clara (10.10.25.10), configure a DNS virtual service and bind it to the g-dns SE group.

  1. Create a virtual service in the Advanced Setup.



  2. Select System-DNS from the Application Profile drop-down menu. Retain the default value of System-UDP-Per-Pkt for the TCP/UDP Profile field.



  3. Click Switch to Advanced in the Service Port section. Add a new port 53. Select the Override TCP/UDP check box and System-TCP-Proxy from the respective drop-down menu.



    Note:

    This step is required if you need DNS over TCP. Pool is not required if you are using Avi Load Balancer DNS for GSLB only and if Avi Load Balancer DNS is not the primary DNS server as mentioned in DNS Virtual Service in the VMware Avi Load Balancer Configuration Guide.

  4. Click Next to navigate to Step 2: Policies.

  5. Configure Network Security rules, if required.

  6. Click Next to proceed to Step 3: Analytics.

  7. Accept the defaults for analytics or change them as shown in the screenshot below:



  8. Click Next to proceed to Step 4: Advanced.

  9. Under Other Settings, select the SE Group g-DNS that was created to host this DNS virtual service.



  10. Optionally create Static DNS Records.



  11. Click Save to complete the process of defining the DNS virtual service for the Santa Clara site.

Repeat the above steps to create a DNS virtual service for the Boston site (10.160.0.20 as per our example). DNS virtual service is named colo-dns with VIP = 10.160.110.100.