Lost DNS and internet connectivity after upgrading to 23.7.4

[ddywz]

My OPNsense was running fine on 23.1.  Once I upgraded to latest 23.7.4 and unit rebooted I lost connectivity and could not get internet connectivity and internal DNS was lost. 

Looking around I had to disable this rule I had for years on FIREWALL---NAT--PORT FORWARDING.  Pic of rule is attached here.  If I disable this rule then external connectivity is fine and I can connect on internet from LAN interface.

Still no internal DNS,  I can no longer ping by name all static reserved addresses I have created.  All this was ok before the upgrade.  I do not use any dnsmasq or OpenDNS.   I have ticked the option to Register DHCP static mapping in Unbound DNS--General.

Any help how to overcome this?  I was planning to roll back to 23.1 but I know I will hit this again if I wanted to upgrade at some point.

[newsense]

The rule is fine. If DNS doesn't work it means there's an issue with your Unbound configuration, so you'll have to expand on that. Screenshots would be fine.

Also, did you try some other resolver in the past and left it around ?

[ddywz]

I have not touched the outbound config.  Always used the automatic as the attachment shows. 

I have not used any other resolver.   On my windows 10 desktop after I flushdns and do an ipconfig /all,  I see external DNS servers on it which is wrong.   

 IPv4 Address. . . . . . . . . . . : 192.168.2.112(Preferred)
   Subnet Mask . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . : Sunday, September 24, 2023 6:48:20 AM
   Lease Expires . . . . . . . . . : Sunday, September 24, 2023 7:50:31 PM
   Default Gateway . . . . . . .  192.168.2.1
   DHCP Server . . . . . . . . . .  192.168.2.1
   DNS Servers . . . . . . . . . .  1.1.1.1
                                             1.0.0.1
   NetBIOS over Tcpip. . . . . : Enabled

Not sure why this changed.  It was showing DNS as 192.168.2.1 before.    All I did is upgraded to 23.7.4

Attached is the Outbound config.

[newsense]

You might be provisioning those DNS entries through DHCP.

Otherwise check if they're not set manually on your machine.


Lastly, what's he output of this command ?

Code: [Select]

nslookup google.com 192.168.2.1

[ddywz]

I managed to get the local DNS working but is weird, some hosts work and some do not.  Something is definitely broken on this release.  I gave up, rolled back to 23.1 and upgraded to latest 23.1.11_2 and restored from a backup from last week.  All working perfect.  Also some plugins are not available in 23.7.4.  I had os-dyndns plugin that is no longer available on this release.

All is working fine for now.

[axsdenied]

Shot in the dark without more diagnostic info:

Might be related to the "Filter Rule association" part.  I checked my entry and it matches yours EXCEPT I don't use any filter rules.  Try setting to "none" and re-enable.  See if works?

[ddywz]

What I will do is get another same exact Qotom Q575-G6 with 16GB RAM and 200GB storage hardware and deploy that with new 23.7 and can play around until all issues are resolved.  That way, if I'm stuck, simply plug back the old device and all is back on-line.  Is not just a matter of providing internet access but I have haproxy there for inbound connections,  DNS, DHCP, VPN server running OPENvpn so there's a lot to fix if something breaks.

Thanks for suggestion,  will try that once I get my 2nd unit to play with.