Packages won't install after config restore

  • Has anyone came up with a method to get Unbound to reload after a config restore?  As it is, requires changing the default DNS from private to public in General Setup, enabling the DNS forwarder, then PfSense has resolution so it can get the Unbound package.  Then the above must be reversed before Unbound is started up or Unbound will stall and a router reboot is required.  So 10 minutes later, rather than 1 minute, the router is back up and running. Very clumsy with Unbound involved.  I've got bit by this doing other than restores as well.

    My thought was to have a cached copy of Unbound stored on the router drive and settings that would look to the drive for packages if it couldn't retrieve them online.

    Is this possible?

Log in to reply