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.

5
  • Have you tried it out? My gut tells me that you might trigger network protections in smarter network gear, and the hosts may prefer to seek out an IP from their previous DHCP server, but the worst case I see is that one of the DHCP servers is ineffective, meaning no redundancy. I suspect it will work okay. Ensuring the DHCP servers stay in sync may be the hard part. Commented Jul 28, 2018 at 5:24
  • No, I haven't tried it yet. Not sure if production network is the proper location for such a trial... On a trial network, such as Linux containers / network namespaces, it could be tried with little difficulty. Perhaps I'll do that. Commented Jul 28, 2018 at 5:27
  • 2
    kb.isc.org/article/AA-00502/0/… Commented Jul 28, 2018 at 7:01
  • DHCP can handle this. ISC DHCPD, for example, has documentation describing how this could be set up. I've not tried it, though, so I don't class this as a proper "answer". (Ah. Just noticed yoonix has referenced the same document.) Commented Jul 28, 2018 at 9:30
  • Related: paulroberts69.wordpress.com/2011/10/27/… and tools.ietf.org/html/draft-ietf-dhc-failover-12 -- it seems it's not an RFC but rather an Internet draft. Commented Jul 28, 2018 at 10:01