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 Universal 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 Infoblox Portal. Also, BloxOne hosts NIOS-X Servers can be configured to service zones that have been synchronized from Azure. For more information about Azure DNS, refer to the Azure DNS documentation.
...
Two-way synchronization of public host -hosted zones and records from between Azure to BloxOne DDIand Universal DDI after the initial configuration and sync is complete. 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 Universal DDI. The synchronized zones are read-only.
Viewing and management of Azure-NIOS-X hosted zones and records through the Infoblox Cloud Services Portal. For more information, see Limitations of Azure DNS Integration.
A BloxOne DDI host NIOS-X Server can directly respond to DNS queries from clients for private zones that are managed in Azure. A BloxOne DDI host NIOS-X Server 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 NIOS-X Servers can be configured to service zones that have been synchronized from Azure. DNS data synchronized from Azure is transferred from the Cloud Services Infoblox Portal to hostsNIOS-X Servers. DNS clients in the enterprise data center can then send queries for Azure DNS–integrated zones to the hostsNIOS-X Servers.
To integrate Azure DNS with BloxOne Universal DDI, complete the following steps:
Go to Configure > Administration > Credentials, and configure Azure credentials. For more information, see Creating Azure Credentials.
Go to DNS > Third Party DNS Providers Configure > Networking > Discovery > Cloud, and configure Azure as a third-party DNS provider. For more information, see Configuring Third Party DNS ProvidersNetwork Discovery.
Go to Configure > Networking > DNS > Zones > Edit Zone, and add an host NIOS-X Server to Azure-synced zones. This step is optional. You can add a host NIOS-X Server to a primary zone or a secondary zone. You can edit the primary zone or secondary zone and add the host NIOS-X Server as an Authoritative DNS Server or add the host NIOS-X Server to a DNS Server Group, and add the group to the primary zone or secondary zone. For more information, see Creating a Primary Zoneor Creating a Secondary Zone.
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 Universal 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 is 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 In this latter case, the vnet-view represents all VNets in the grouping.
...