Bug #4061
open
dhcpd doesn't send client-hostname to peer, breaking DHCP lease registrations w/HA
0%
Description
In a HA setup with DHCP server enabled, both peers will assign IPs. The leases that sync to peers don't include client-hostname. Where DHCP registration to DNS is enabled, each system in a pair only knows the hostnames for leases it issued, leaving name resolution of DHCP hostnames about 50% broken (half will work on the primary only, other half work on the secondary only).
a dead-end discussion of this issue:
https://lists.isc.org/pipermail/dhcp-users/2009-February/008329.html
dhcpd likely needs fixed.
This is something that will almost certainly be post-2.2, but putting to 2.2 for the moment in case we can find a quick fix.
Updated by Chris Buechler about 10 years ago
- Target version changed from 2.2 to 2.2.1
no quick fix here, will review further for 2.2.1
Updated by Chris Buechler almost 10 years ago
- Target version changed from 2.2.1 to 2.2.2
Updated by Chris Buechler over 9 years ago
- Target version changed from 2.2.2 to 2.2.3
Updated by Chris Buechler over 9 years ago
- Target version changed from 2.2.3 to 2.3
Updated by Jim Thompson about 9 years ago
- Assignee set to Anonymous
Assigned to Steve Beaver (to give him a break from the GUI)
Updated by Anonymous almost 9 years ago
- Status changed from Confirmed to Feedback
- Priority changed from High to Normal
On researching this and discussing it with other DEV team members, the issue arises from the current expected behavior of ISC-dhcpd. Not fixable in pfSense.
Updated by Chris Buechler almost 9 years ago
- Status changed from Feedback to Confirmed
- Assignee deleted (
Anonymous) - Target version deleted (
2.3)
it'd either require changes in dhcpd or redoing how we register DHCP leases in DNS. Either way is non-trivial.
Updated by David Erickson almost 8 years ago
It looks like this may have been fixed upstream in version 4.3.5, is this something that could be easily tested? Happy to help if so.
See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810971
https://lists.isc.org/pipermail/dhcp-users/2016-October/020331.html
Updated by Jim Pingle almost 8 years ago
4.3.5 is in pfSense 2.3.3 and 2.4. Just update and try it.
Updated by David Erickson almost 8 years ago
Jim Pingle wrote:
4.3.5 is in pfSense 2.3.3 and 2.4. Just update and try it.
Ah bummer, I did my testing on 2.3.3 so if it is in there it didn't fix it.