Greetings,
I did a test install of 27.RC1 and updated to RC2. I reinstalled my backup from 26.1.11_6. However, It seems the DNS redirect to Unbound became non-functional. Any clues?
So - A bit more "upgrade testing" may have uncovered a quirk related to my above issue of DNS. In the General settings for Unbound, the item "Network Interfaces" is set as "All Interfaces". After the update to 26.7.x this selection was now blank, empty as it were. I had to put check marks against "all" of my interfaces - WAN, LAN & OPT to make it equivalent to the former setting.
(Corrected version number above - erroneously had 27.7. We are not quite there yet.)
"All interfaces" is still the empty selection, but it shows as "Nothing selected". I'm not sure if that's a recent change, but technically they are the same in any case.
Cheers,
Franco
PS: could be from https://github.com/opnsense/core/commit/3d9cccfe4038802807219621ddd49cf668a05144 -- we'll look into it
Filed via https://github.com/opnsense/core/issues/10533
So - Have fully updated to 26.7.1-1, all works well except DNS redirect to Unbound. Unbound works well as a DNS if I choose it as my primary DNS.
Suggestions please - I've tried various redirect rules to no avail.
See, https://forum.opnsense.org/index.php?topic=9245.0 - especially see to it that you do not create a loop to itself.
So - some fiddling - I can see a DNS redirect message in the live log but ... no DNS data gets returned. Rolled back to 27.1 and all works perfectly. My setup is a transparent bridge if that makes any difference on an APU3-4. I reviewed the rules etc as indicated above but no luck. Rules are all migrated to the "new" rules format on 27.1.x and they work.