Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • Multiple DHCP servers on a network will by no means knock a network out. In fact, multiple DHCP servers are a common feature of resilient networks. Now what can cause problems for clients are multiple DHCP servers handing out IP addresses from the same address pool, and/or with conflicting settings (e.g. differing DNS servers, gateway, etc.) Commented Mar 11, 2017 at 17:02
  • @Twisty, yes, I think that was implied.
    – Darren
    Commented Mar 11, 2017 at 17:04
  • You indicate adding a DHCP server will cause a packet storm, knocking out the network. How exactly would the packet storm occur? Commented Mar 11, 2017 at 17:06
  • @twisty, it's been a while now, but I have seen with my own two eyes someone connect a rogue DHCP server to our network and knock it out. From memory, it seemed to be caused by every client simultaneously trying to renegotiate their lease and a storm of ARP broadcasts as multiple clients were receiving duplicate IP addresses (one from each server) and subsequently trying to renegotiate.
    – Darren
    Commented Mar 11, 2017 at 18:01
  • I have no doubt that a malicious DHCP server could impact a network's operation. But that's quite different than asserting that a competent administrator will experience problems with multiple DHCP servers. Large networks require multiple such servers! Commented Mar 11, 2017 at 18:13