I know this is ludicrously old, but we're running into a similarly veined issue here.

There may be something unique to your environment that makes them reluctant to pursue this approach. It might be worthwhile going back to your network team and asking what sorts of 'issues' that they feel the implementation of DHCP relaysВ would cause. On any network segment where you're using DHCP relays, the local server needs to be disabled. At worst, you will have a mix of acceptable responses and a lot of potential for conflicting addresses. If you have a mixture of local DHCP servers and relays, the local servers will respond faster and may not provide the configuration you want to deploy. The clients are going to broadcast for the first DHCP server that answers with an acceptable offer, which they will take. In most environments, there isn't a problem with doing this, but it isВ a majorВ architectural consideration and not something you just turn on without consideration.В This is largely because DHCP works on a broadcast principle. Having a few servers with a central DHCP configuration for all segments is a good management proposition. Larger organizations will frequently use this approach in order to avoid having to manually edit DHCP configurations at the router or switch level. It's very common to use DHCP relays (IP helpers) in order to centralize DHCP infrastructure.

Starsector technology cache