Forward mDNS traffic into container

I’m having a user project (user-901) in which I have profiles, networks and containers.

The containers in question are network-connected via an incus-bridge (incusbr-901) and in their own network, having access to the host and outer network (possibly the internet) via NAT.

Now I want the containers to also receive and process mDNS traffic which the host is receiving on its physical network interface (let’s say wifi0).

I already tried to reflect/forward mDNS traffic from my host’s interface (wifi0), which receives the mDNS traffic and incusbr-901, but that apparently doesn’t cut it.

I do not need, actually I do not want it at all, mDNS traffic originating from within containers to get forwarded/reflected out of their NAT’ed network to the host, but only want outer mDNS traffic to be accessible by the containers.

I guess you need wide area bonjour. I just found it by search engine.
https://serverfault.com/questions/136133/bonjour-mdns-broadcast-across-subnets

http://www.dns-sd.org/ServerSetup.html

Can the containers be moved out from behind NAT?

I get that this might “solve” the issue, but no, the containers have to stay behind the NAT and the question is indeed about reflecting/forwarding mDNS-traffic - at least this way/direction - into the NAT/containers.