Azure DNS is a cloud DNS web service that routes end users’ requests to internet applications and resources by resolving domain names into IP addresses and IP addresses into domain names. In Azure, DNS records are organized into hosted zones, which are configured through the Azure API, Azure CLI, or Azure Resource Manager.
BloxOne DDI provides the capability for synchronizing and integrating public-hosted zones with Azure, and this allows users to view and manage Azure DNS data through the Cloud Services Portal. Also, BloxOne hosts can be configured to service zones that have been synchronized from Azure. For more information about Azure DNS, refer to the Azure DNS documentation.
The Infoblox Azure DNS integration feature offers the following:
Two-way synchronization of public host zones and records from Azure to BloxOne DDI. Synchronization of Azure DNS resource records configured with a simple routing policy is supported. Other routing policies are not supported. Synchronization of DNSSEC records is not supported.
One-way synchronization of private zones from Azure DNS to BloxOne DDI. The synchronized zones are read-only.
Viewing and management of Azure-hosted zones and records through the Infoblox Cloud Services Portal. For more information, see Limitations of Azure DNS Integration.
A BloxOne DDI host can directly respond to DNS queries from clients for private zones that are managed in Azure. A BloxOne DDI host can be configured as a secondary DNS server for local clients thereby reducing the network load since the queries do not need to recurse to Azure DNS.
The following diagram illustrates how to leverage the BloxOne Azure DNS integration feature. In an architecture that consists of on-premise networks and an Azure public cloud, BloxOne hosts can be configured to service zones that have been synchronized from Azure. DNS data synchronized from Azure is transferred from the Cloud Services Portal to hosts. DNS clients in the enterprise data center can then send queries for Azure DNS–integrated zones to the hosts.
To integrate Azure DNS with BloxOne DDI, complete the following steps:
Go to Administration > Credentials, and configure Azure credentials. For more information, see Creating Azure Credentials.
Go to DNS > Third Party DNS Providers, and configure Azure as a third-party DNS provider. For more information, see Configuring Third Party DNS Providers.
Go to DNS > Zones > Edit Zone, and add an host to Azure-synced zones. This step is optional. You can add a host to a primary zone or a secondary zone. You can edit the primary zone or secondary zone and add the host as an Authoritative DNS Server or add the host to a DNS Server Group, and add the group to the primary zone or secondary zone. For more information, see Creating a Primary Zone or Creating a Secondary Zone.
All Azure DNS private zones are associated with a VNet in Azure. Each VNet represents a private network. It is quite possible that within one Azure tenant there are overlapping networks and zones between VNet. Therefore, to avoid conflict errors in BloxOne DDI, a new DNS view will be created for each VNet grouping that is synced. Zones with each VNet grouping will be added within the DNS view that has been created for each respectively. It is expected that in most cases, the VNet grouping will consist of a single VNet. However, for the cases where a zone is assigned to multiple VNets, the grouping would include all VNets assigned to the zone. In this latter case, the vnet-view represents all VNets in the grouping.