KEA DHCP missing "Register DHCP leases in DNS Resolver..."
-
@noloader said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
I have to admit I am disappointed. I am on the stable release branch. I am not on a testing/experimental/development branch. The pfSense team should keep KEA DHCP separate from stable until KEA DHCP is ready for production.
Kea is stable and its functionality well-documented. merely lacking subjectively-expected features doesn't make software unstable.
and no, 'registering' DHCP leases into a local zone file is not a critical function of a DHCP server. (in fact, it's not even a thing outside the context of pfSense.)
-
@cyberconsultants,
Disagree.
-
@noloader with?
-
@cyberconsultants said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
not even a thing outside the context of pfSense
Windows Server can do it. :) But yeah most routers don't.
I would have worded the warning to say something about Kea being in a preview and to link to the release notes.
-
@SteveITS Windows Server does a lot aside from provide DHCP and DNS services. and Kea's not a router—it's a DHCP server.
-
@cyberconsultants said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
Kea is also not in preview
I know Kea isn't, it is in pfSense:
https://docs.netgate.com/pfsense/en/latest/releases/23-09.html#kea-dhcp-server-feature-preview-now-available -
@SteveITS and opt-in.
-
I also updated to version 2.7.1, now 2.7.2, also on the stable branch.
In the settings there a warning that ISC has reachted EOL and that the DHCP backend should be switched.
It was not visible to me that there are breaking changes here, functions that are simply omitted.
Sorry to say that. Surely this is documented somewhere, but here it is suggested that you can simply change it.
I switched back to ISC and waiting that are the function will be present for Kea. -
@noloader I can relate to this. I upgraded to 2.7.2 and then upgraded to Kea DHCP. My problem was much as you described. DHCP leases were correctly being leased as expected but didn't seem to register with the DNS resolver. Working through the settings I couldn't find anywhere in the config relating to this. I have reverted to the original ISC DHCP service and once I set the register leases with the DNS Resolver everything came back to life. Kea seems to be a bit bleeding edge to me or I have not worked out some of the settings relating to Kea. Not a clean upgrade that's for sure.
-
Limitations of the “Kea preview” are in the release notes linked above.
Agree it would be better if the note in pfSense GUI mentioned it was a preview…it’s come up in other threads but to paraphrase, “the note about ISC being deprecated is correct.”
-
This post is deleted! -
@SteveITS Thanks for the feedback Steve, I struggle to see the value of Kea DHCP for anyone using an internal DNS resolver. Without the 2 hooked up together where DHCP registrations get registered in DNS can only be a backward step. I assume features are going to be added to Kea DHCP to support this sort of functionality before ISC DHCP is discontinued.
-
Exact.
Kea has very extended possibilities to act upon every DHCP related events.
A future pfSense release will use (I guess) fire up this one so it will use unbound-control in its turn to 'insert' DNS info into the resolver (unbound) without the need for unbound restarts as it was the case with ISC DHCP. -
I had the same but slightly different issue when I upgraded to Kea DHCP - I was finding that it would resolve some of my devices and not others and this was very confusing. As a test, I added the default domain name (localdomain in my case) in DHCP Server setting for each network (although the text says that it would do this by default anyway and I should not have to enter it if using the default domain configured in System > General Setup > Domain Name). As soon as I applied this change, DNS resolver was able to resolve all my devices. Just thought I'd share it in case it helps anyone, although one shouldn't need to do this and is a workaround at best. Looking forward to seeing this fixed and the option to register DHCP leases being made available in the next release.
-
@noloader Hi, I have the same need as yours. Is there a way to make a rolback for isc?
-
@frankz said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
Is there a way to make a rolback for isc?
Click use ISC where you changed it to use KEA
-
@Johnpoz Thank you , I had focused on the menu of the dhcp server .!!!!! Thank you .
-
the fact that Kea DCHP doesn't have this feature is a deal breaker. I too have reverted to ISC.
I wish this lack had been communicated better that this feature was missing. It was very disruptive to many as they didn't know what was causing DNS to fail.
The deprecation warning should have mentioned Kea isn't at parity with ISC.
-
@manny-tew said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
I wish this lack had been communicated better that this feature was missing
You mean like in the release notes that goes over what is not working yet.. With the big Warning box ;)
https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#rn-2-7-1-kea
https://docs.netgate.com/pfsense/en/latest/releases/23-09.html#rn-23-09-kea
And also notice in the same place tells you how to just switch back there at the bottom, etc..
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 24.11 | Lab VMs 2.7.2, 24.11 -
@johnpoz said in KEA DHCP missing "Register DHCP leases in DNS Resolver...":
I wish this lack had been communicated better that this feature was missingYou mean like in the release notes that goes over what is not working yet.. With the big Warning box ;)
A small nit... The GUI does not provide the information before, during or after an upgrade. And there is no link to the release notes document.
On the Home page, there's just a "Version X.X.X is available," with a little cloud (download) button to click. On the System Updates page, there's just a version number and confirm button to click.
So I think it is fair to say "better communicated" since no communication is going on at the moment for those who are upgrading using the GUI.
