samba - recently started misbehaving after 6.0.42 or 6.0.43 updates

I've been using OMV since version 3, doing fresh installs of 4, 5 and now 6. I am not a linux noob, but I don't consider myself an expert either.

My initial install of 6 worked fine, but somewhere in the last update or two (6.0.43-1 is the version I am running, but the last 2 updates ended up getting installed just a day apart for me so I'm not sure exactly which version the problem started in) samba seems to be misbehaving a little.

I have a docker container with dnsmasq that I use for local dns, and have been using this container for the life of my OMV5 install and the last few months when I installed OMV6. I have several dns entries such as address=/nas/192.168.2.250 for local access and address=/fully.qualified.doman.name/192.168.2.250 for web access to some docker based web apps and a nextcloud VM, so that internal and external addresses appear to be the same. (I have not typed the FQDN here for privacy purposes and will use FQDN henceforth) Prior to using dnsmasq, I used to use hosts file entries on windows.

I used to be able to see all my shares from windows explorer by typing \\nas, but now I am getting an error as shown in the following attachment. I tried \\nas\share also, but I get the same error. However, if I preface the FQDN I mentioned above with nas (\\nas.FQDN), it works, even though I don't have that explicitly defined.

Has something changed recently that is requiring an FQDN to access the samba shares, or has broken the short name access? Is there something I am missing that someone can suggest. A setting to check? etc.

I have done the usual omv and windows reboots, windows ipconfig /release, /renew, and /flushdns

Thanks in advance

Looks like my issue was actually dns related. The dnsmasq contianer I was running for local dns was seeing and logging dns queries from my network, but for some reason the results of the queries were not being passed back to the devices. I suspect a recent change in kvm/libvirt, or something else in the OMV host software is creating the issue, but it wasn't worth going down the rabbit hole to find out.

So, rather than chasing my tail for weeks, I just ran up a small Debian 11 VM and installed pihole on it. Now I have my local dns working correctly again, and I have a network wide ad blocker too. This way is isolated from OMV, so hopefully no further problems.