Book a quick demo Get in touch Give us a call

Migrating to cloud? Retain critical DHCP service on site

As internet connectivity becomes ubiquitous, companies are increasingly migrating IT infrastructure from physical servers to cloud-based solutions like AWS or Azure. This makes sense for most of the services in an organisation's data centre/server room, reducing complexity and costs with little difference in the services themselves.

But some infrastructure, including DHCP, is unavailable on popular cloud platforms and, in any case, is too critical to migrate and leave at the mercy of a Single Point of Failure: the internet connection.

It's likely that you're using Windows Server for DHCP services and, with this solution available in Azure, cloud migration is often prompted by a Windows Server refreshment project. Whilst you can move other Windows Server functionality to Azure, DHCP is not supported. With such a high maintenance burden, it doesn't make sense to retain an on-site instance of Windows Server solely for DHCP.

Diagram of three different kinds of DHCP setups- 1. A Microsoft server between users and the internet (local DHCP), 2. The internet between users and Microsoft Azure (cloud DHCP), 3. Diagram number 2 with DNSBOX between users and the internet (local DHCP)

DNSBOX offers a cost-effective on-site alternative that additionally enables you to deploy a High Availability pair of DHCP servers and that customers describe as "DHCP at it's finest".