DNS Server Configurations for the Aviatrix Controller

This page provides guidance on configuring the DNS server for the Aviatrix Controller. The Aviatrix Controller requires DNS resolution to communicate with various services, including: Licensing, CoPilot services, telemetry services, Public APIs, and optional integrations.

By default, the Controller uses Google Public DNS servers. This ensures that DNS resolution is reliable and independent of customer-specific network configurations. However, in environments with private DNS requirements or restricted outbound access, using the DNS server provided by the VPC/VNet DHCP option may be more appropriate.

Configure DNS server for the Controller

To configure the DNS server for the Controller:

  1. Go to Settings > Configuration > General in the Aviatrix CoPilot user interface.

  2. Locate the DNS Server for Controller tile.

Configuration Options

Aviatrix Default DNS Server (Default)

The Aviatrix Default DNS server uses Google Public DNS servers.

This option is suitable for environments with unrestricted internet access and ensures the Controller has consistent and reliable DNS resolution regardless of customer infrastructure.

Cloud VPC/VNet DNS Server

This option uses DNS servers configured through the VPC/VNet DHCP options. By enabling this option, Aviatrix Controller can leverage the DNS servers provided by the Virtual Private Cloud (VPC) or Virtual Network (VNet), ensuring that DNS queries are resolved within the cloud infrastructure. This setup is particularly beneficial for environments where Controller need to interact with cloud-based resources and services.

Recommended for environments that require:

  • Resolution of private domain names.

  • DNS routing through internal enterprise infrastructure

  • Compliance with organizational policies that restrict access to public DNS servers