I'm not a user of Infoblox...but another IPAM/DNS vendor's tool (actually, have been for over 15 years).
We have multiple forests...1 forest has the IPAM/DNS vendor's product integrated with DNS (not DHCP - MS/DHCP is used) - the other forests do not. With the one forest that it is integrated - we have hundreds of people who can do IPAM/DNS entries without impacting anything other than their own "stuff" (rights to IP addresses/names on the subnets). In the other forests - we use MS/DNS and MS/DHCP. In those areas - only my team (domain admins) manage the entries...and we do many many manual entries each day in those other environments (24x7). Rarely do we have to do 24x7 DNS changes in the forest where the other IPAM/DNS tool operates. So IMO - it boils down to how many people need to use this tool versus how many are using MS/DNS and MS/DHCP? If this will enable more end-user 'self service' so that your team can do other things (or the business gets their changes implemented faster by doing it themselves) - is that of greater value than the cost of the tool (don't forget to factor in implementation, training and ongoing annual support). Good luck! From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Wednesday, June 25, 2014 4:50 PM To: [email protected] Subject: [NTSysADM] Infoblox vs. native Windows A proposal is floating around here about ditching native DHCP and DNS on Windows server in favor of Infoblox. Looking for pros/cons, comments, experiences please.
