Document toolboxDocument toolbox

Limitations of NIOS object sync

Owned by Sri Raghu
Sept 06, 2024
1 min read

There are some limitations of the NIOS object sync:

  • Only the objects, actions, and attributes listed in NIOS objects supported for sync can be managed through the Infoblox Portal.

  • When creating a primary zone (authzone) or a secondary zone in a NIOS DNS view, the option Notify External Secondary DNS Servers is not supported.

  • Compartments are not supported.

  • All data synced from NIOS belong to a single federated grid.

  • DNS Server Groups are not supported when creating zones.

  • When creating a primary zone (authzone) in a NIOS DNS view, queries, zone transfer, and updates are not supported.

  • When creating a secondary zone (authzone) in a NIOS DNS view, zone transfer is not supported.

  • The Lock option in NIOS is not supported when managing from Universal DDI.

  • When syncing objects from NIOS, only Grid Primary is synced. Grid Secondary is not supported.

  • If an External Primary is configured in NIOS, and a Grid Secondary is configured as well, only then will the Grid Secondary be synced to the Infoblox Portal.

  • Name Server Group from NIOS cannot be managed from Universal DDI.

  • The Stealth field from NIOS is not supported in Universal DDI.

  • If a NIOS object is sent to recycle bin using the option Move to Recycle Bin, it will be deleted from both NIOS and Universal DDI. However, the deleted object cannot be restored.

  • If a NIOS object is sent to recycle bin using the option Move to Recycle Bin, Reparent Child Objects feature is not supported.

 

Â