Project

General

Profile

Actions

Bug #4061

open

dhcpd doesn't send client-hostname to peer, breaking DHCP lease registrations w/HA

Added by Chris Buechler over 6 years ago. Updated over 4 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
12/02/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

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.

Actions #1

Updated by Chris Buechler over 6 years ago

  • Target version changed from 2.2 to 2.2.1

no quick fix here, will review further for 2.2.1

Actions #2

Updated by Chris Buechler over 6 years ago

  • Target version changed from 2.2.1 to 2.2.2
Actions #3

Updated by Chris Buechler over 6 years ago

  • Target version changed from 2.2.2 to 2.2.3
Actions #4

Updated by Chris Buechler about 6 years ago

  • Target version changed from 2.2.3 to 2.3
Actions #5

Updated by Jim Thompson over 5 years ago

  • Assignee set to Steve Beaver

Assigned to Steve Beaver (to give him a break from the GUI)

Actions #6

Updated by Steve Beaver over 5 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.

Actions #7

Updated by Chris Buechler over 5 years ago

  • Status changed from Feedback to Confirmed
  • Assignee deleted (Steve Beaver)
  • 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.

Actions #8

Updated by David Erickson over 4 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

Actions #9

Updated by Jim Pingle over 4 years ago

4.3.5 is in pfSense 2.3.3 and 2.4. Just update and try it.

Actions #10

Updated by David Erickson over 4 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.

Actions

Also available in: Atom PDF