Inheritance settings applied to Route53 synced zones
- Sri Raghu
BloxOne Inheritance setting can be applied to Route53 synchronized zones and records. For more information describing BloxOne Inheritance, please refer to the About DNS Inheritance section of the Infoblox online documentation. Not all inheritable settings are synchronizable to Route53. Generally speaking, settings that do not synchronize to Route53 are labeled in the primary zone create and edit dialogs. An example of one such label is shown below:
Zone Transfers are not applicable to Third-Party DNS Providers.
Settings marked with a not applicable label indicate that the setting(s) do not synchronize with AWS. If, however, a zone is assigned to both an AWS Third-party DNS provider and a Universal DDI NIOS-X Server, setting(s) changes in that zone are still applicable to the Universal DDI NIOS-X Server.
Zone settings
Most zone settings are synchronized with Route53 (Refresh, Retry, Expire, Default TTL, Negative-caching TTL, Email Address (For SOA RNAME field)). The exceptions are:
Primary Name Server (For SOA MNAME Field)
Use default forwarders to resolve queries for delegated subzones.
Â
Records
Resource record TTL is inheritable and synchronized with Route53. Therefore, any changes to the TTL value directly on the record or in the inheritance chain will be *synced to Route53. The serial number of the SOA record is not a syncable field. Any changes made to the SN of the SOA record, whether it be due to an edit change or a natural increment due to zone-related changes, are not synchronized to Route53.