Upgraded to 2.7.2 today...DHCP and DHCPv6 are No longer working...
-
I think I have fixed it...
It appears that the 2.7.2. upgrade changed this setting:
To this:
The upgrade had to have made this change - as I rarely ever got into DHCP settings for either protocol.
-
Hmm, what did you upgrade from?
-
2.7.1 >> 2.7.2
Dashboard had been prompting me for about a week that 2.7.2 was released.
-
Hmm, and you were already running Kea there?
-
Indeed.
I am now having other looksies and finding these White and Green arrows are not consistent. All of these with the RED - are ON, and ONLINE and I can ping them. But none of them will resolve in a DNS LOOKUP, which is quite ODD. They all used to. It appears that just about everything (unless it is a Windows box) no longer works in DNS LOOKUP from Diagnostics >> DNS Lookup (images below).
This one is the pfSense - and I would expect it to work:
This one - however does not (it is ONLINE):
but from it's Terminal screen I can ping pfSense and it resolves them:
-
The arrow colour there just reflects the state in the ARP table. So if that host hasn't sent or received any routed traffic recently it may show as down.
Kea cannot currently add dhcp hostnames to the DNS resolver so they cannot be resolved like that. If you need to be able to resolve dynamic hostnames you should sitch back to the ISC DHCP server for now.
-
Are there steps to change it back from KEA? or do we know when it will be fixed?
Thanks for all your assistance.
-
@bearhntr see the paragraph under the orange here: https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#kea-dhcp-server-feature-preview-now-available
-
You can just switch back. There shouldn't be anything else required.
Yeah Kea is not technically broken it just doesn't have that feature yet.
-
OK...made the switch and even rebooted. Got some more GREEN Arrows - still not all accurate as to ONLINE servers - but I guess I just wait.
Still does not DNS resolve names for existing DHCP reservations into IP. Still getting this error (does same with FQDN or just Hostname):
In fact even cleared the ARP table - and it immediately rebuilt - and nothing resolves except the pfsense
Me soooooo - cornfuzed -
@bearhntr I'd guess you need to wait for a lease renewal on the device, so the IP is added to unbound. Try restarting the device, or unplug/reconnect.
-
Your firewall and the dhcp clients share the same domain I assume?
Can it resolve by fqdn?
-
Yes...at the moment. pfSense is directly from Cable ISP - all traffic goes through it. It handles all DHCP and DNS, but is configured to FWD unknown DNS requests to CloudFlare (for IPv4 and IPv6).
FQDN does not resolve either.
I will give another check tomorrow and see if the expirations have occurred and it then works.
-
Hmm, do you have 'DHCP Registration' enabled in the DNS Resolver config? You might try resaving the resolver settings to restart the dhcpleases script that updates the hosts.
-
They were 'checked' - I unchecked, and SAVED, then re-checked and SAVED
....annnnnnd lookie there, already working:
-
Guess it will take a while for the IPv6 to pick it up.
-
