Page Comparison

...

• Synchronization of DNS data from your AWS VPCs and AWS GovCloud VPCs to the NIOS database (note that this is a one-way synchronization).

• Synchronization of DNS data from multiple AWS accounts of an AWS organization to NIOS by using a single NIOS cloud admin account. You can synchronize the DNS data of all child accounts in an AWS organization or, from NIOS 9.0.4 onwards, configure the list of child accounts for which the DNS data must be synchronized.

• A unified console (Grid Manager) across your enterprise networks and AWS hosted zones.

• Consolidated DNS and IPAM views for all DNS data through Grid Manager.

• Seamless synchronization of DNS data that is updated or deleted in AWS to the NIOS database.

The below diagram illustrates how you can utilize the Infoblox Amazon Route 53 integration feature to achieve centralized DNS data visualization. In a Grid that consists of on-premise networks and an AWS public cloud, you define two Grid members to which Route 53 data is synchronized. The DNS data is synchronized from Amazon Route 53, and then transferred from the members to the Grid Master to be stored in the NIOS database. DNS clients (in the enterprise data center) can then query NIOS for the imported Route 53 DNS data. You can also view the imported DNS data through Grid Manager. Note that all synchronization is done at the hosted zone level from Amazon Route 53 to NIOS, NOT vice versa.

...

...

Each hosted zone supports a resource record set that includes records such as A/AAAA, Alias, PTR, NS, SOA, MX, TXT, CNAME, SRV, and SPF. In the Amazon Route 53 GUI, you can view resource record details such as record name, record type, TTL value, record value, and routing policy. Resource records imported from Amazon Route 53 to NIOS are mapped to their corresponding NIOS resource record types, except for SPF records. Amazon Route 53 SPF records are mapped to TXT records in NIOS.

...