Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Azure DNS with BloxOne DDI has the following limitations:

  • BloxOne DDI does not support Azure DNS tags.

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

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

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

  • SOA records synchronized from BloxOne DDI to Azure may take several sync intervals to update. The SOA details that support synchronization are refresh, retry, expire, negativeTTL, rname, and defaultTTL.

  • Azure Alias records are synchronized into BloxOne DDI as CNAME or A records depending on the alias target type. Azure alias records pointing to the zone apex are not supported as the DNS protocol does not support CNAME records referring to the zone apex.

    • Azure Front Door Resources:

      • Converted to B1DDI CNAME Records

      • properties.cName field stored as CNAME in B1DDI

    • Azure Traffic Manager:

      • Converted to B1DDI CNAME Records

      • properties.fqdn field stored as CNAME in B1DDI

    • Azure CDN:

      • Converted to B1DDI CNAME Records

      • properties.hostName field stored as CNAME in B1DDI

    • Public IP:

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

      • properties.ipAddress field stored as address in B1DDI

      • empty does not create any record

    • Static Web App:

      • Converted to B1DDI CNAME Records

      • properties.defaultHostname field stored as CNAME in B1

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

  • No labels