Conflict in managing zones with the same FQDN in different views through Shared Record Group in Info

[#1]

I am encountering an issue while using the Infoblox APIs to manage two DNS zones with the same FQDN (for example, example.com) but in two different views (e.g., Internal and External). The goal is to associate both zones with a Shared Record Group to share certain DNS records between the two zones.

When I attempt to create the Shared Record Group by specifying both zones in the zone_associations field using the API, Infoblox is unable to distinguish between the two zones with the same FQDN. The API does not allow specifying which view each zone belongs to, causing a conflict. Infoblox returns an error because it cannot properly manage zones with the same name but in different views within the zone_associations field.

Here is the error that is generated when I try to execute the API:

{ "Error": "AdmConDataError: expected single object, got 2",
  "code": "Client.Ibap.Data",
  "text": "expected single object, got 2"
}

The Infoblox graphical interface allows zones with the same FQDN but in different views to be correctly associated with the same Shared Record Group without issues. However, this operation cannot be replicated through the API.

If you need further details or clarification, feel free to reply to this comment for more information.

[#2 · Accepted solution]

This is a known limitation of the API when managing zones with the same FQDN across different views. The API cannot distinguish between the zones, leading to atf booru conflicts during the creation of Shared Record Groups. It's advisable to check the Infoblox documentation for any updates or contact support for possible workarounds or to request this feature enhancement.