Any word on the Unbound integration
-
Hi guys,
I know that there is work being done to integrate Unbound into 2.1….as far as I can tell it's actually almost done as I can view the configuration if I edit my pfsense url to go to /services_unbound.php or /services_unbound_advanced.php.
It looks like the only things missing are the pages to edit the host & domain overrides and listing it in the services menu. Any idea when the final push to glue it all together will happen?
-Will
-
You can find host and domain overrides below the advanced section of the Services:DNS Forwarder section.
I presume that's what you're looking for? -
Hi rcfa,
No, I'm asking about progress on a replacement\ alternative to the existing DNS Forwarder called "Unbound". You can find more details about it here:
http://doc.pfsense.org/index.php/Unbound_package
It used to be a package you could add to an existing install but a around 6 months ago it was removed out of the available packages list because there was an effort underway to add it into pfSense itself. I don't know if it was planned to replace the existing forwarder package with it or to have it included as optional.
That said, there were a bunch of commits to 2.1 back in early April and it looks like the program is ready to be tested\used except for a few bits that are needed to make it visible in the GUI and to edit the host & domain overrides. That or it could have been found to be horribly broken and the devs just haven't had a chance to pull it back out!
Either way I'm just looking for an update on the status because it's a package I am very much looking forward to using!
-Will
-
Uhm, sure. I knew about the first part. I just didn't pay close attention to the URL, and thought it was already active, but it still seems to be DNSmasq rather than Unbound…
...still, if you need the functionality now.I hope the fact that the menu entries are generic (DNS Forwarder) means that a switch-over can be fairly transparent, but that may also be one of the problems: since one can upgrade from 2.0.x to 2.1.x somehow the settings need to be converted so no bad things happen during the upgrade.
