Amazon Route 53 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 Amazon Route 53, DNS records are organized into hosted zones, which are configured through the Route 53 API, AWS CLI, or AWS Management Console.
BloxOne DDI provides the capability for synchronizing and integrating public-hosted zones with Amazon Route 53, and this allows users to view and manage Route 53 DNS data through the Cloud Services Portal. Also, BloxOne hosts can be configured to service zones that have been synchronized from Route 53. For more information about Amazon Route 53, refer to the Amazon Route 53 documentation.
The Infoblox Amazon Route 53 integration feature offers the following:
Two-way synchronization of public host zones and records from AWS Route 53 to BloxOne DDI. Synchronization of AWS 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 AWS Route 53 to BloxOne DDI. The synchronized zones are read-only.
Viewing and management of AWS-hosted zones and records through the Infoblox Cloud Services Portal. For more information, see Limitations of AWS Route 53 Integration.
A BloxOne DDI host can directly respond to DNS queries from clients for private zones that are managed in AWS Route 53. 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 AWS Route 53.
The following diagram illustrates how to leverage the BloxOne Route 53 integration feature. In an architecture that consists of on-premise networks and an AWS public cloud, BloxOne hosts can be configured to service zones that have been synchronized from Route 53. DNS data synchronized from Amazon Route 53 is transferred from the Cloud Services Portal to hosts. DNS clients in the enterprise data center can then send queries for Route 53–integrated zones to the hosts.
To integrate AWS Route 53 with BloxOne DDI, complete the following steps:
Go to Administration > Credentials, and configure Amazon Route 53 credentials. For more information, see Creating AWS Route 53 Credentials.
Go to DNS > Third Party DNS Providers, and configure Amazon Route 53 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 AWS-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 Route 53 private zones are associated with a VPC in AWS. Each VPC represents a private network. It is quite possible that within one AWS tenant there are overlapping networks and zones between VPC. Therefore, to avoid conflict errors in BloxOne DDI, a new DNS view will be created for each VPC grouping that is synced. Zones with each VPC grouping will be added within the DNS view that has been created for each respectively. It is expected that in most cases, the VPC grouping will consist of a single VPC. However, for the cases where a zone is assigned to multiple VPC's, the grouping would include all VPC's assigned to the zone. In this latter case, the vpc-view represents all VPCs in the grouping.
You can perform the following actions: