Document toolboxDocument toolbox

Limitations of Azure DNS Integration

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

Azure DNS with BloxOne DDI has the following limitations:

  • BloxOne DDI does not support Azure DNS tags.

  • Universal DDI does not provide support for the creation of Multiple Third Party DNS providers for the same Azure Subscription ID.

  • Universal DDI does not support non-simple routing policy records.

  • Universal DDI only supports static credentials for Azure right now.

  • Azure supports multiple values for a resource record set. After data synchronization, BloxOne DDI creates multiple records (one for each value that is specified in Azure).

  • Universal DDI does not allow updates or deletions to NS records synchronized with Azure since it is a system record.

  • SOA records synchronized from Universal DDI to Azure may take several sync intervals to update. The SOA details that support synchronization are refresh, retry, expire, negative TTL, RNAME, and default TTL.

  • The MNAME field is not synchronized between Azure and BloxOne DDI, nor is the Serial Number.

  • Following are the Azure supported alias records and corresponding conversions in B1DDI:

    • Azure Front Door Resources:

      • Converted to Universal DDI CNAME Records

      • properties.cName field stored as CNAME in Universal DD

    • Azure Traffic Manager:

      • Converted to Universal DD CNAME Records

      • properties.fqdn field stored as CNAME in Universal DD

    • Azure CDN:

      • Converted to Universal DD CNAME Records

      • properties.NIOS-X Server name field stored as CNAME in Universal DD

    • Public IP:

      • Converted to IPv4/IPv6  Record as per the target source

      • properties.ipAddress field stored as address in Universal DD

    • Static Web App:

      • Converted to Universal DD CNAME Records

      • properties.defaultNIOS-X Server name field stored as CNAME in B1