FWIW, I’m more supportive of this approach for IP only services… But more food for thought here, than specific recommendations…
I get the “all VLAN” approach, but for stuff that really only does Layer 3/IP stuff, you really don’t need ANY bridge. A DNS server container (or web server, storage server, etc) does NOT need Layer2.
So you can also treat VETH IP address more like you would Wireguard instead – you give the each VETH some unique subnet to use, just like you do on for WG interface. Perhaps thinking about the VETH IP as the “WG peer” address, and the gateway address as the “WG interface” address may be more helpful at explaining this approach. So what you use as the gateway address in the VETH for a container, is what you’d set in /ip/address for the VETH. And the IP/subnet you use for VETHs should be one you are NOT using elsewhere in your network.
A DNS Server (or most container) only “EXPOSE” a few IP ports. So in some ways this make the firewall configuration maybe easier, since you can refer use the VETH as the src-interface or dst-interface (or it’s IP address) in your firewall rules. The indirection of any bridge makes the firewall rules a tad more complex IMO.
But you may want to do this since it make the “all VLAN” config consistent, at the expense of slightly more complex firewall rules. So not wrong a design to run all contiainer’s VETH’s through the main vlan-filtering=yes bridge as bridge ports.
And since some container do need Layer 2, and those need to be some bridge. That be another arguement for just always using a new VLAN for each container, since it provide consistency. If we take another example, like the netinstall container here: http://forum.mikrotik.com/t/guide-running-netinstall-server-on-a-tik/161056/1 that does needs to be in a bridge, since need to bridge some physical port with the netinstall container for it to work! And those instructions can be adapted similarly to a PVID and bridge port, instead of create a separate bridge. And you’d adapt the above Pi-Hole example, to create some VLAN 97 for a netinstall container.
And some container may even NEED to be on a vlan-filtering=yes bridge. For example, the various mDNS proxy container – these need to listen for multicast on MULTIPLE VLANs, so the container needs to be configured as a TRUNK port to do so & inside the container it’s actually VLAN aware (most container are NOT VLAN aware, so they act as access ports). See here: http://forum.mikrotik.com/t/mdns-repeater-feature/148334/179