The biggest thing for Infoblox to improve isn't so much from a technology perspective. Their biggest problem is with the corporate side of the house as far as getting a support response or getting a sales team response isn't always as efficient as it should be and as it used to be.

How you track IPs within a subnet and how all of that works was not intuitive to me. If I compare it to VitalQIP, I create a subnet, and it's a slash 24 size. It's very easy. I look, and here are my 254 IPs. I can then see if I have assigned a static, do I have a DHCP scope, and what's the name of the device. That's all there in front of me. The thing that I found frustrating with Infoblox was that it was not very intuitive. There were certain things you could add, which I thought were confusing. It did not have a similar layout. You could add something as a normal object and you would get the DNS name, the IP address, and what's called a NAPTR record, or there was also something where you could just add a DNS entry tool, just the A record, but you won't necessarily see all of those showing up easily in a subnet. In summary, the graphical interface for showing what IPs are defined in a subnet was not very intuitive. It could have a better look and feel to it.

Infoblox IPAM has improved and is better, but it needs to have an external GSLB functionality. Currently, the solution has a GLSB functionality for internal appliances, but for an external user, that functionality doesn't exist.

Infoblox IPAM also needs some improvement on its threat engine and RPZ policies, or DNS firewall or DNS policies.

An additional feature I'd like to see in Infoblox IPAM is zero-touch provisioning in terms of the appliances. Currently, there's zero-touch provisioning for cloud-based devices, but for physical appliances in branches, there's none, so you still have to do some configurations. For example, if you have existing DNS infrastructure and you need to set up Infoblox IPAM in new branches, and you need more appliances, you should be able to just plug the solution into the network, and there shouldn't be any manual interference required.

The challenge I faced was to extract the VLAN data or all the IP address details, but we were able to troubleshoot that. That was because I didn't have the rights. So, my automation team wrote a script. 

When we do a host entry, it also reflects in the lookup. We should be able to filter that part. If we do only the A and PTR records, we need to reflect only that part in the lookup.

From an IPAM standpoint, DHCP is an area that needs to be improved.

When we use the forwarders or when we're trying to connect to the internet, sometimes there are issues and the publishing time is longer. We want a robust mechanism so that creating records doesn't take that much time. It currently takes about one hour to duplicate things from our local network to the internet.

The security could be enhanced. There should be more detailed encoding so messages cannot be taken by a third party. It's encoded on our side, but we need to make it more complex because there are many sources that are able to decode it. If there is the smallest leak, then it's a beta problem.

In the next release, the UI could be improved. I would like to see a simpler version or a customizable UI.

The only room for improvement in Infoblox IPAM is its compatibility and flexibility with IPv6. There's been an issue transitioning from IPv4 to IPv6, and though Infoblox is in the process of resolving the issue, it would be better if the team could come up with a solution in a quicker timeframe.

Better transitioning from IPv4 to IPv6 is what I'd like to see in the next release of the solution.

Infoblox IPAM could improve some of the features. The market is demanding for some features that are not there, but there is always a reason why it's not there. At the moment, the solution is rather complete for what it's used for. It can always extend to solve some other issues that are linked to it, but the solution itself is complete.

CLI needs to be user-friendly. There should be an option to commit changes. 

We were using a Palo Alto firewall for global connect, and by default, Palo Alto firewall has to have a local IP pool for handing out the IP address. So, we would like to see integration between the Palo Alto firewall, other firewalls, and Infoblox IPAM so it can read what VPN clients have disconnected and then remove the DNS entries for those clients. Then Infoblox IPAM can remove any stolen DNA records as it sometimes creates many problems.

The solution is not easy to use; the GUI and CLI are challenging to use, limiting end-user capability. We can't use Linux terminal features with Infoblox, as it struggles to detect and troubleshoot problems. We generally use troubleshooting tools like tcpdump in our network security area and we can use that in Infoblox with limited features. 

The solution's GUI requires improvement; all the features fall under just a few top menus, making it challenging to find the feature I'm looking for promptly. I use other products like Fortinet FortiGate and an F5 network solution, which feature much better GUIs to find what I'm looking for easily. The Infoblox GUI isn't necessarily hard to use but isn't straightforward, either. Ultimately, the GUI is acceptable, but the CLI needs improvement. A better CLI would save time for the end user and increase their capability with the solution.

The scope of our use of this solution is limited to the DDI IPAM solution for Infoblox. This solution could be improved by offering multiple integrations with IPAM which could already exist but we aren't aware of them. 

An area for improvement is IPAM's smart folders, which can be slow to access and would benefit from a search feature. In the next release, IPAM should include a separate view for requests and descriptions for tabs.

The marketing of the solution could improve to give customers the awareness of the benefits.