AWS Route 53 integration with BloxOne DDI has the following limitations:
BloxOne DDI does not support Route 53 tags.
BloxOne DDI does not support non-simple routing policy records.
Amazon supports multiple values for a resource record set. After data synchronization, BloxOne DDI creates multiple records (one for each value that is specified in Route 53).
SPF records from Route 53 are not synchronized with BloxOne DDI.
BloxOne DDI does not allow updates or deletions to NS records synchronized with AWS Route 53 since it is a system record.
SOA records synchronized from BloxOne DDI to AWS Route 53 may take several sync intervals to update. The SOA details that support synchronization are refresh, retry, expire, negative TTL, mname, and default TTL.
AWS Route 53 Alias A records are synchronized into BloxOne DDI as CNAME records. Route 53 alias records pointing to the zone apex are not supported as the DNS protocol does not support CNAME records referring to the zone apex.
The MNAME field is not synchronized between AWS Route 53 and BloxOne DDI, nor is the Serial Number.
Synchronization initializes the RNAME field to the R53 value. After the first-time sync, the RNAME value can be changed/managed on either side (R53 or B1) and synchronized.
BloxOne DDI does not provide support for the creation of multiple Third Party DNS providers for the same AWS Account ID.