@jlw52761 said in Unbound with DHCP Registration Very Slow:
Sorry, but this is supposed to be an Enterprise grade product, this type of bug is not acceptable in a feature that's been core to the product for a number of years.
Interesting.
pfSense is a (nearly native) FreeBSD kernel and uses pf which is part of the the kernel.
Both are open source.
The whole is enveloped with a nice GUI, and add to to that, a lot of network related features are added.
A pretty complicated things became easy to handle on first sight. But it's still a 'Enterprise grade product' needing 'Enterprise grade product' knowledge
@jlw52761 said in Unbound with DHCP Registration Very Slow:
So if I have to do static leases, what the hell's the point of DHCP in the first place?
You misunderstood static leases : all network clients still use the default dhcp client. The DHCP server is still needed.
Only the admin decides now what IP every device gets.
@home this isn't' really needed, but for an company or enterprise, this is a must have, as I'm not going to run around on every floor to set a static IP for every new device that comes in.
For info : I'm using pfSense since day one, and actually rarely handle DHCP stuff.
I do have a 'map' in pfSense - nice centralized in one place - where every device has its IP and host name that I choose, like Android-William, instead of seeing this :
edit : wait ... 'a couple of thousands of workstations' .. you already know all this.
[image: 1726033701534-6337b4e1-08c5-4e4f-9ecb-4fda30420780-image.png]
@jlw52761 said in Unbound with DHCP Registration Very Slow:
I am very disappointed in this product at this point.
Just wait a couple of .. what .. weeks, and this situation will be something of the past.
You'll get over it, as the other million or so users ^^
@jlw52761 said in Unbound with DHCP Registration Very Slow:
Since I have a lot of DHCP clients and would like to use .... ..... more stable like Bind.
bind9 is the full solution and can do more as unbound. It is available as a pfSense package.
pfSense needed a resolver, was using a forwarder (its still there, in case of), and unbound was chosen.
unbound is stable, though. Its just the "DHCP lease to DNS" integration that was somewhat quirky.
As said, that will be addressed very soon.
Btw : I'm using bind myself for the classic "domain name" services on a Debian server. Using the good old config files method, as interfacing bind with a GUI is just IMHO, plain impossible.
@jlw52761 said in Unbound with DHCP Registration Very Slow:
I have the default of 7200 for the lease time
Another factor : Wifi devices that go off range, come into range, etc every time they come back, a DHCP request is fired ...
If you have 'thousands' of devices that your DHCP server, on all of its interfaces, will see many request per minute.
The "DHCP Registration" isn't an option for you, that's for sure.
With that number of devices, I probably would use the firewall as the firewall, and use a dedicated DHCP server for my internal needs. And even outsource locally DNS also.
@jlw52761 said in Unbound with DHCP Registration Very Slow:
Also, still can't find in the logs that Unbound is restarting, so curious on that and how long it's taking to restart
Look in the unbound (Resolver) logs ?
[image: 1726034845876-5d8e761d-04c1-4371-b501-acf760728a0a-image.png]
[image: 1726034815058-ec2edb72-92cd-413d-983f-243903fb33b6-image.png]
2,5 seconds.
I'm using pfBlockerng with a couple of hundreds of thousands DNSBL ...
edit :
Posted a couple of hours ago :
https://forum.netgate.com/topic/189752/is-24-08-on-track/28?_=1726035419944
Read the bug report ... its .. yeah, you have (and get the) point.
