Versions Compared

Old Version 1

changes.mady.by.user Sri Raghu

Saved on

compared with

New Version Current

changes.mady.by.user Sri Raghu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Azure DNS with BloxOne DDI has the following limitations:

  • BloxOne DDI does not support Azure DNS tags.BloxOne

  • 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).

  • BloxOne Universal 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 Universal DDI to Azure may take several sync intervals to update. The SOA details that support synchronization are refresh, retry, expire, negativeTTLnegative TTL, rnameRNAME, and defaultTTLdefault TTL.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.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 B1DDI Universal DDI CNAME Records

      • properties.cName field stored as CNAME in B1DDIUniversal DD

    • Azure Traffic Manager:

      • Converted to B1DDI Universal DD CNAME Records

      • properties.fqdn field stored as CNAME in B1DDIUniversal DD

    • Azure CDN:

      • Converted to B1DDI Universal DD CNAME Records

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

    • Public IP:

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

      • properties.ipAddress field stored as address in B1DDIempty does not create any recordUniversal DD

    • Static Web App:

      • Converted to B1DDI Universal DD CNAME Records

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

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