Update to 22.1.5 removes all Unbound Aliases!

[PotatoCarl]

Hi
the update today from 22.1.4 -> 22.1.5 removes all Host-aliases in Unbound!
How can I reinstall them?
How can I unencrypt the cloud saved version?
Thank you.

[franco]

Short version: it doesn't. We are looking into the issue. For now you can:

# opnsense-revert -r 22.1.4 opnsense


Cheers,
Franco

[PotatoCarl]

Ok.
2nd time in a row that an update has problems.
Just have sent an error report additionally as it seems there is more than this problem.

Instead of going back to 1.5 I'll try to ride this out and see if it will work (spent some hours getting the aliases back into the system)

[Taomyn]

I've had to revert after finding most of my services not starting, the console would never finish loading so no direct access even the serial console, the GUI was running and I was able to start most services but Unbound just refused no matter what.


Fortunately I was still able to SSH into the firewall, added 8.8.8.8 to resolv.conf and reverted to 22.1.4_1 - all is well again

[aimdev]

Hi
the update today from 22.1.4 -> 22.1.5 removes all Host-aliases in Unbound!
How can I reinstall them?
How can I unencrypt the cloud saved version?
Thank you.

Prior to the update did you take a local backup of the configuration?, if so then you should be able to recover the unbound configuration.

[franco]

I'll say it again: configuration isn't gone, but unusable on 22.1.5 in the current state. Revert to 22.1.4, it works as confirmed by others who also gave their configuration in support. We do appreciate this a lot and I see none of it here.

This year in particular we seem to have nobody running development versions who could report on these issues that have been there for weeks up front. It's unfortunate but it's our reality as much as everyone else's.

We decided some major versions ago that we would bundle changes in development systems for at least one release cycle or more so consumers of the development version could report issues if they arise.

The PPPoE IPv6 issue in 22.1.4 was on development version, the Unbound migration was there too. Nobody saw it and we do have A LOT of active installations out in the wild...


Cheers,
Franco

[Mks]

Dear all, may I was lucky.

My Alias are still there, updated today from 22.1.4_1 to 22.1.5

br

[aimdev]

My aliases are available, however they are not apparent on the unbound page which has a changed layout.
They are also in the json file produced prior to the upgrade, so all is not (unless you have no local backups)

[mfpck]

This year in particular we seem to have nobody running development versions who could report on these issues that have been there for weeks up front. It's unfortunate but it's our reality as much as everyone else's.

We decided some major versions ago that we would bundle changes in development systems for at least one release cycle or more so consumers of the development version could report issues if they arise.

The PPPoE IPv6 issue in 22.1.4 was on development version, the Unbound migration was there too. Nobody saw it and we do have A LOT of active installations out in the wild...

Cheers,
Franco

I am not really aware of dev. versions and I think it is pretty intrasparent also to find them upfront especially for new users because it seems not to be write anywhere really.

The dev. versions are just available for already installed versions of Opnsense, right ?
There are no dev. iso images upfront or daily snapshots like pfsense did ?

Form my understanding and based on your strategy the current version was always considered as community edition which may could make issues due it's beeing ....and for more critical setups the business edition ?

[chemlud]

System -> Firmware -> Settings -> Type -> Development

;-)

[franco]

An open secret. ;)

Much of this is sticky information on the latest release forum since 2016: https://forum.opnsense.org/index.php?topic=2084.0

I'll make sure to update it for 2022 and make things more explicit. But I accept that people run development, community or business for their very own reasons. All we have to do is offer all of them to choose from.


Cheers,
Franco

[netnut]

Short version: it doesn't. We are looking into the issue. For now you can:

# opnsense-revert -r 22.1.4 opnsense

Before I did a revert because of this issue I took a moment to play with the 'new' GUI.

I noticed that using the "Domain Form" in 22.1.5 does have the 'old' help text "To use a nondefault port for communication, append an '@' with the port number." but fails to validate the input (No valid IPv4/IPv6 address).

So something like "127.0.0.1@53530" couldn't be configured/validated in the new form.

[franco]

Yes, this is https://github.com/opnsense/core/commit/ff11cde38e8 and we will be issuing 22.1.6 this week to address the Unbound issues in 22.1.5.


Cheers,
Franco

[netnut]

...and we will be issuing 22.1.6 this week to address the Unbound issues in 22.1.5.

Woeha! Missed that fix, I need to learn using "is:issue is:closed unbound" @ GitHub. Didn't realize you're even squashing bugs at weekends :-)

[Condor]

i had done  opnsense-revert -r 22.1.4 opnsense, then to 22.13, then to 22.1.2, tried different settings backup, there is no case. unboun DNS is not starting.

I had to change the dhcp DNS server to google's ones, because the router IP is not working since updated to 22.1.5