Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

Is there a standard that allows a device on a network to have its own DHCP server that only gets turned on if there is no other DHCP server on the network? I'm sure it's possible to implement one using dhcp_probe but I was wondering if there's a pre-existing way of doing this.

share|improve this question

marked as duplicate by RobM, yagmoth555, Jenny D, Tim Brigham, Jim B Mar 3 at 17:38

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

You might find… useful. – RobM Mar 22 '13 at 22:28

No, there is no standard for this. There are some dhcp servers that provide a intelligent fail over, and others who don't at all.

99% of dhcp deployments just use more than one server, as the client will respond to the first offer it gets. One popular way of prioritize them is by using delayed response on the non-primary one.

share|improve this answer

One typical way of running multiple servers is to only hand out half of the addresses on the subnet/scope from one server and then the other half from another server. Your pools have to be over sized handle one server completely failing. Aside from that it works well with minimal setup.

As pauska said, there is no standard though.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.