I'm running into an odd issue with unbound.
Recently upgraded to pfSense 2.1, ripped out some multi-WAN
configuration due to the fact that our second WAN has gone away. The
interface still exists, but is disabled and all routing and gateway
failover has been removed.
Primary WAN does rely on DHCP.
After a pfSense reboot, unbound does not come up. I'm also unable to
start the service using the services manager, but if I go to the unbound
dialog, change nothing and click "Save", it starts immediately and
functions well.
dnsmasq is completely disabled -- We were only using it because it did a
better job of splitting load across the two WANs, otherwise unbound
looks like a far better solution.
--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
