Skip to content

Instantly share code, notes, and snippets.

@zealfire
Created May 12, 2018 22:34
Show Gist options
  • Save zealfire/78e8896c0f490a5c6be9d52be1ea42be to your computer and use it in GitHub Desktop.
Save zealfire/78e8896c0f490a5c6be9d52be1ea42be to your computer and use it in GitHub Desktop.
DHCP Failover is a mechanism whereby two DHCP servers are both configured to manage the same pool of addresses so that they can share the load of assigning leases for that pool, and provide back-up for each other in case of network outages.
Failover partnerships are configured per pool, so one DHCP server may have several active partnerships with different peers. The configuration elements of DHCP Failover are to establish peering relationship first (via the failover peer declarations in dhcpd.conf), and then to establish which pools will use the partnership by adding the failover peer option to the pool declarations individually.
For more information and a sample configuration, please refer to: A Basic Guide to Configuring DHCP Failover
dhcpd will only accept inbound TCP connections from its configured failover peers
But note that the dialogue between failover partners is neither encrypted nor authenticated. Since most DHCP servers exist within an organization's own secure Intranet, this would be an unnecessary overhead. However, if you have DHCP failover peers whose communications traverse insecure networks, then we recommend that you consider the use of VPN tunneling between them to ensure that the failover partnership is immune to disruption (accidental or otherwise) via third parties. Your local firewalls should also be configured to prevent access to the failover port by unauthorized devices.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment