Hostname empty and not resolvable

peoples

Hello,

running pfsense 2.3.3-p1 with one dhcp on LAN interface.
I've many clients with exact same image (ubuntu) and often i see empty hostname fields on dhcp leases page.
Also this hosts are not resolvable by other clients. For me this seems to be random.

Is there any known issue ?

Thanks
regards

peoples

no one else with this problem ?

gjaltemba

What dhcpd version is running?

Upgrade ISC dhcpd to 4.3.5 to address missing hostname workaround

https://redmine.pfsense.org/issues/6840

peoples

dhcpd –version returns isc-dhcpd-4.3.5 .

Also tried the old workarround with dhcp-cache-threshold 0 , but this doesn't seem to work.

peoples

Hm .. i'm runnin carp configuration .. and it seems like all missing hostnames have entries like this in dhcp system log


DHCPREQUEST for 10.0.8.150 (10.0.0.2) from 7c:2b:e1:07:b9:76 via igb1: lease owned by peer

so if lease is owned by other carp member no hostname is available and therefore this client isn't resolv able by dns .. is this a normal behaviour ?

peoples

i disabled the dhcp peer state - stopped dhcp service on both boxes and cleared the dhcpd.leases file on both boxes.
after enable dhcp service and enable failover peer ip lease was still empty .. first boot of a client .. and the dhcp on the CARP Backup box registered the dns and the primary box says "lease owned by peer "

Skew on primary box is 0
Skew on secondary box is 100

strange, isn't it ?

peoples

here is the dhcpd.conf from secondary node:


option domain-name "lab.inet";
option ldap-server code 95 = text;
option domain-search-list code 119 = text;
option arch code 93 = unsigned integer 16; # RFC4578

default-lease-time 7200;
max-lease-time 86400;
log-facility local7;
one-lease-per-client true;
deny duplicates;
ping-check true;
update-conflict-detection false;
dhcp-cache-threshold 0;
authoritative;
failover peer "dhcp_lan" {
  secondary;
  address 10.0.0.3;
  port 520;
  peer address 10.0.0.2;
  peer port 519;
  max-response-delay 10;
  max-unacked-updates 10;

  load balance max seconds 3;
}

subnet 10.0.0.0 netmask 255.255.240.0 {
        pool {
                deny dynamic bootp clients;
                failover peer "dhcp_lan";
                ddns-update-style interim;

                range 10.0.0.100 10.0.15.254;
        }

        option routers 10.0.0.1;
        option domain-name "lab.inet";
        option domain-name-servers 10.0.0.3;
        default-lease-time 2592000;

}
ddns-update-style interim;
update-static-leases on;

and here from primary node:

option domain-name "lab.inet";
option ldap-server code 95 = text;
option domain-search-list code 119 = text;
option arch code 93 = unsigned integer 16; # RFC4578

default-lease-time 7200;
max-lease-time 86400;
log-facility local7;
one-lease-per-client true;
deny duplicates;
ping-check true;
update-conflict-detection false;
dhcp-cache-threshold 0;
authoritative;
failover peer "dhcp_lan" {
  primary;
  address 10.0.0.2;
  port 519;
  peer address 10.0.0.3;
  peer port 520;
  max-response-delay 10;
  max-unacked-updates 10;
  split 128;
  mclt 600;

  load balance max seconds 3;
}

subnet 10.0.0.0 netmask 255.255.240.0 {
	pool {
		deny dynamic bootp clients;
		failover peer "dhcp_lan";
		ddns-update-style interim;

		range 10.0.0.100 10.0.15.254;
	}

	option routers 10.0.0.1;
	option domain-name "lab.inet";
	option domain-name-servers 10.0.0.2;
	default-lease-time 2592000;

}
ddns-update-style interim;
update-static-leases on;

ypanier

Hi,

I have exactly the same issue with 2.3.4 and previously with the 2.3.3

The lease than the client retrieve is shown in DHCP Leases on master/slave but the hostname is only shown on the server who gave the lease

To resolve the behavior i tried :

disable dns forward / resolver
disable dhcp server
run pfSsh.php playback disabledhcpd
rm /var/dhcpd/var/db/dhcpd.leases*
reboot both slave and master
reconfigure the dhcpd service

It seems that the problem is well known :

https://lists.isc.org/pipermail/dhcp-users/2016-October/020331.html

It seems that these bug was resolved in 4.3.5 (version installed on pfsense) but continue to encounter it

Anyone have an idea or patch ?

best regards,

johnpoz

"Hm .. i'm runnin carp configuration"

And why did you not mention that in post 1 would be my question..

peoples

@ypanier:

Hi,

I have exactly the same issue with 2.3.4 and previously with the 2.3.3

The lease than the client retrieve is shown in DHCP Leases on master/slave but the hostname is only shown on the server who gave the lease

To resolve the behavior i tried :

disable dns forward / resolver

disable dhcp server

run pfSsh.php playback disabledhcpd

rm /var/dhcpd/var/db/dhcpd.leases*

reboot both slave and master

reconfigure the dhcpd service

It seems that the problem is well known :

https://lists.isc.org/pipermail/dhcp-users/2016-October/020331.html

It seems that these bug was resolved in 4.3.5 (version installed on pfsense) but continue to encounter it

Anyone have an idea or patch ?

best regards,

temp. i disabled dhcp sync in CARP and also disabled second DHCP server to get arround this. :(