Unbound issues continues - time for change
-
PFsense + 25.07.1 and Unbound log full of start and stop.
I am using KEA DHCP. I was hoping that this old issue would be resolved in this version.Screenshot 2025-10-31 at 3.07.02 PM.png
I wish that Unbound was a complete separate package. This way we can simply update Unbound when new release has been compiled.
DNS is an important part of the network infrastructure and this would be best. I dont know why sometime ago the decision was made otherwise but maybe now it is time to rethink that decision.Second, DHCP server should not be interacting with Unbound. What is the reason? Unbound does not care if you client IP is static or not.
This current integration between the two does not make sense. If you think about large networks were DNS server is deployed on a separate hardware, DHCP server has no business dictating and modifying Unbound files.For many years now I have been running Unbound DNS on a Synology Docker. Super, super stable and I never have issues. I can compile new version as soon as it is available. I have a mix of static and DHCP clients and it all works great.
We should keep things simple and separate the two on pfsense. Hope someone there is listening.
-
This post is deleted!
