Page tree


  • Ensure that the time on the NIOS or vNIOS appliance is synchronized with the actual time so that AWS Route 53 synchronization functions properly.
  • Depending on the number of hosted zones and resource records, the synchronization of Route 53 data could consume significant amount of memory and database capacity. Therefore, when you configure the Grid member to pull Amazon Route 53 data, ensure that the Grid member has the capacity to handle bulk import of DNS data. Infoblox suggests that you select a member that is not running other services and can handle the synchronization load for this feature.
  • To reduce unnecessary data synchronization and to ensure optimal performance in your Grid, use filters to specify the hosted zones that you want to import into the NIOS database when you configure sync tasks. For information about how to configure sync tasks, see Configuring Amazon Route 53 Sync Groups.
  • Hosted zones imported from Amazon Route 53 are managed by Route 53 only. If you add or manipulate any Route 53 DNS data in NIOS, the changes will be overwritten in subsequent synchronization with Amazon Route 53. Infoblox recommends that you do not add or modify any Route 53 data through NIOS.
  • NIOS does not synchronize Route 53 data to a network view whose authority is delegated to another Grid member. When you configure a sync group, ensure that you select a network view that is not delegated.
  • Amazon Route 53 zones and records cannot be synchronized to NIOS database when a zone is signed as they are encrypted.

  • Amazon supports multiple values for a resource record set. After data synchronization, NIOS create multiple records (one for each value that is specified in Route 53).
  • NIOS does not import NS and SOA records for Route 53 hosted zones. When you configure a primary and secondary name servers to serve Route 53 hosted zones, NIOS creates the NS records and use the default SOA records for these zones.
  • SPF records from Route 53 are stored as TXT records in NIOS.
  • NIOS does not support the following Route 53 data:
    • Duplicate records (or records using the same name and same record type) in a hosted zone using "non-simple" routing policies
    • Duplicate Route 53 public hosted zones
    • "Tags" in Route 53 (similar to extensible attributes in NIOS)
  • During creation of Route 53 record, name with special characters < or are not allowed.
  • No labels

This page has no comments.