---
title: "Limitations of IPAM, DHCP and DNS Management in Multi-Grid Manager"
canonical: "https://docs.infoblox.com/space/MAG8/1099530364/Limitations%20of%20IPAM%2C%20DHCP%20and%20DNS%20Management%20in%20Multi-Grid%20Manager"
format: markdown
---
Following are the limitations in IPAM, DHCP and DNS Management in Multi-Grid Manager:

- On Multi-Grid Manager version 9.0.7, from the **IPAM** tab you can drill-down till the IP address level (IP list and Map), but the associated details are not displayed until you enable object change tracking in the sub Grid to which the network belongs. After object change tracking is enabled, you must wait for the DNS and DHCP synchronization to complete. You can then view the associated details in the IP list or Map drill-down screens. You must also enable synchronization for DNS views for DNS objects to be displayed in Multi-Grid Manager.  
  
You can enable object change tracking by using the **Object Change Tracking **option in the *Grid Properties Editor. *For detailed information about object change tracking, see [Tracking Object Changes in the Database](https://infoblox-docs.atlassian.net/wiki/spaces/nios90draft/pages/73292044) in the NIOS documentation.
- The following objects are not supported in Multi-Grid Manager: DNS Traffic Control, DHCID, Shared, and DNSSEC records.
- RPZs, auto-created and secondary zones are not supported.
- IPv4 and IPv6 discovered data are not supported.
- Global search option is not supported for DNS and DHCP and IP -level objects.
- User permissions for non-super user and object level permission for DNS, DHCP and IP level are not supported.
- Name Server (NS) records are not synchronized with Multi-Grid Manager for DNS zones assigned to the name server group.
- When a Grid is disconnected and then rejoined to the Multi-Grid Manager, new keys are generated. Upon reverting to the Grid, you will need to disconnect and rejoin the Grid  to Multi-Grid Manager once again due to a key mismatch between the Multi-Grid Manager and the Grid.
- The Single Sign On (SSO) navigation for a selected network on the DHCP page directs to IP Map of that network, instead of directing to DHCP networks page.