BloxOne inheritance settings applied to GCP DNS synced zones

BloxOne Inheritance setting can be applied to GCP-synchronized zones and records.  For more information describing Universal DDI inheritance, please refer to the About DNS Inheritance.  Not all inheritable settings are synchronizable to GCP.  Generally speaking, settings that do not synchronize to GCP 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 GCP.  If, however, a zone is assigned to both an GCP Third-party DNS provider and a NIOS-X Server, setting(s) changes in that zone are still applicable to NIOS-X Server.

Zone settings

Most of the zone settings are synchronized with GCP (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 GCP.  Therefore, any changes to the TTL value directly on the record or in the inheritance chain will be synced to GCP.  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 GCP.