If you have an established network with existing Microsoft DNS/ DHCP servers already in place, you may not want to replace them with a full DDI appliance solution:
![]() |
|
However, there are several major shortcoming of relying on Microsoft DNS and DHCP services: there are no interactive tools available for efficient real-time management of IP space; migrating to Azure leaves gaps in local DHCP service.
Retain Windows DNS/DHCP and add IP Address Management (IPAM)
You need an IPAM solution that will: 1) automate the day-to-day manual processes, 2) give you full control over the use of your IP space, and 3) synchronise with your live DNS and DHCP data.
Simply purchasing a separate IPAM platform would address the first two requirements, but your entire network infrastructure would remain disjointed. So, you need an IPAM solution with the flexibility to integrate with your existing Microsoft infrastructure, like DNSBOX.
Implementing an IPAM solution on top of your existing Microsoft DNS/DHCP will allow you to:
- See all changes made in MS AD DNS
- Make static DNS entries to AD Zones
- Configure and manage MS DHCP servers
At the same time, your DNS/DHCP setup will remain unchanged, so you won’t end up paying to replace anything you don’t need to.
If your networks are mixed – with both Microsoft and non-Microsoft areas (“*nix”), integrated DDI allows you to obtain a single view of your networks, while allowing the different parts to be managed to fit different needs.
And if, in future, you decide that you have the scope to extend the IPAM solution to include DNS/DHCP services, a flexible DDI appliance will make it easy for you to do so.
Replace Windows DHCP when migrating to Azure
Organisations moving Windows Server infrastructure to Azure or other cloud platforms frequently encounter an unexpected consequence: DHCP for on-premises devices must stay local, but the Windows Server that was running it has moved to the cloud. Azure does not provide DHCP services for on-premises clients. The result is an urgent need for a dedicated on-prem DHCP server — often at short notice, mid-migration. DNSBOX is a common solution in this situation: it replaces the DHCP role of the departed Windows Server, requires no additional OS licensing, and can be deployed and configured quickly without disrupting the rest of the migration.
![]() |

