Upgraded to 2.7.2 today...DHCP and DHCPv6 are No longer working...
-
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.
-
