Deployment Scenarios

This section focuses on how you can direct client traffic to the Avi Load Balancer DNS service.

Authoritative Name Server for a Subdomain (Zone)

One of the most common ways to ensure that traffic reaches the Avi Load Balancer DNS service is to delegate a subdomain to the Avi Load Balancer DNS service on your corporate DNS server. The corporate name server delegates one or more subdomains to the Avi Load Balancer DNS service, which in turn acts as an authoritative DNS server for them.

In the example shown below, avi.acme.com and gslb.acme.com are the subdomains. Typically, the corporate name server will have a Name Server (NS) record pointing to the Avi Load Balancer DNS service (10.100.10.50). Client queries for these subdomains are sent directly to the Avi Load Balancer, whereas all DNS requests outside of acme.com are instead sent to the external .com name server.

Primary Name Server for a Domain

Avi Load Balancer DNS responds to any zone it has been configured to support in this case, where there is a primary name server for a domain with pass-through to the corporate name server. DNS queries that do not match Avi Load Balancer DNS records pass through (proxy) to corporate DNS servers via a virtual service pool created for this purpose. If members of that pool receive DNS requests outside the corporate domain (in this case, acme.com), they send them to their external .com name server.