Document toolboxDocument toolbox

Inheritance settings applied to Azure DNS synced zones

Owned by Sri Raghu
Last updated: Sept 06, 2024
1 min read

Inheritance setting can be applied to Azure DNS synchronized zones and resource records. For more information about Inheritance, please refer to the About DNS Inheritance. Not all inheritable settings are synchronizable to Azure DNS.  Generally speaking, settings that do not synchronize to Azure DNS 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 Azure DNS.  If, however, a zone is assigned to both an Azure DNS 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 Azure DNS (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 Azure DNS. Therefore, any changes to the TTL value directly on the record or in the inheritance chain will be synced to Azure DNS. The serial number of the SOA record is not a syncable field.  Any changes made to the serial number 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 Azure DNS.