IPAM For Microsoft DNS and DHCP servers

Modern network infrastructures require complete control of core network services and IP plan foundations. While Microsoft’s IPAM brings some basic capacity for IP Address Management, it requires a dedicated server and is unsuitable for today’s open architectures. Missing APIs removes capability for automation & external actions, lack of a true repository causes IP address conflicts, and multiple DNS/DHCP modification points delays IPAM synchronization. In addition, companies face difficulties when trying to scale and to deploy state-of-the-art high availability.