Anyone using this version got mDNS working? If YES please tell me how ...

I have CCR1009 with 5 vlans that's connected to my CRS326 switch where all my vlans reside either through ethernet or WiFi
I want my printer that is AirPrint capable and sitting in vlan100 to be accessed by any apple device siting in vlan20
This should be doable with mDNS but in my case the apple devices using vlan20 cannot communicate with the printer.

According to normis configuring mDNS is very simple
on my CCR1009 via terminal I issue:
/ip/dns set mdns-repeat-ifaces=vlan100,vlan20

is there something else thats needs to be configured using mDNS? because this does not work ... my apple devices cannot see the AirPrint capable printer

I've done a couple test and seems to work.

But since mDNS just provides an IP address, one way it can go wrong is if the firewall blocks the resulting connection.

On Mac (and some Linux and Windows with Bonjour installed), you can use:
to see any mDNS records for printers (IPP), which help confirm mDNS is arriving.

Thanks Amm0 ... I have not had any luck so far

My understanding is that mDNS is crucial for facilitating device discovery and communication within local networks without the need for a dedicated DNS server ... but Tik have not explained how that is implemented under RoS ... why introduce a new feature without some form of direction that is not puzzling .... rhetorically stated ...

AFAIK, it looks like RouterOS just copies the mDNS UDP packets between the selected interface.

It's roughly same approach as viewtopic.php?t=204025&hilit=mdns. Just implemented at a low-level.

Basically RouterOS will look for mDNS if configured in /ip/dns, then re-broadcast any mDNS the router gets on ANY of the mDNS interface to ALL of the configuration mDNS interfaces.

So it's not some flexible mDNS "router", at this point, it just copies/mirror/repeats everything bi-directionally. The reason why this get more complex is if you want to define "one-way" repeating (i.e. mDNS flows uni-directionally). Right now, basically, you can create ONE mDNS discovery zone, that "shares" everything between the interfaces configured in /ip/dns. Perhaps more is planned, but I think that's what it does in beta3.

In fairness, I did one test of this... between a remote EoIP to my folk house. If enable this 7.16 mDNS repeat in /ip/dns, I can see and control a Roku TV at least. So we'll have to wait for Mikrotik to say more on what it should do... All I can see is what a 15 minute tested showed .

The remote EoIP and local network are both just in "LAN" interface-list, so there are no VLAN restrictions. If you restrict VLANs... you have to allow both mDNS for input, and whatever protocol used by the device in forward. That part isn't changed by repeating mDNS, the firewall still has to allow whatever traffic, even multicast.

While Apple AirPrint should work find being "repeated". I'm not sure AirPlay works if repeated due to DRM concerns - I dunno for sure (since a HomePod already deal with the apple things). So I didn't test AirPlay, but that not working, would not be a surprise. i.e. Apple AirPlay may need a src-nat NAT rule between VLANs (for AirPlay) since the source IP is unicast & I believe it enforces that AirPlay MUST be on same LAN. So repeating the mDNS doesn't help when trying to play music/movie – maybe this has changed. But testing AirPlay with this feature would not be a good "first test".

OT: @Amm0, have you connected two remote locations using EoIP with interface added to the Bridge (and eventually VLAN ID), or assigning an Address to EoIP and adding routing rule?
MTU? Mangle rules?
If you prefer I can be more specific with the question posting in viewtopic.php?t=206322

Correct, in my test case. There RB1100AHx4 that hangs on my LAN that I use for mainly for testing beta/devices from work. I have one EoIP link on that RB1100 that is a /interface/bridge/port on BOTH sides - it bridges my folk's remote LAN bridge (from a cAPac that acts as both the AP and router, with an EoIP tunnel (to RB1100)). On the RB1100, there is a /ip/dhcp-client that pull my folk's LAN IPs on to the RB1100, and one additional port is tagged to same VLAN as EoIP.

It seems to allow you set mDNS repeat on the EoIP interface, but unless both sides had that bridged with an /interface/vlan... I'm not sure there be a use case for repeating EoIP directly. Even though there is EoIP involved, it's bridged to a LAN/VLAN on both sides - so it's LAN/VLAN that needs to be included in mDNS repeating.

FWIW, While I have no need for printer between these "sites"... I did verify my Mac on my local LAN see my Mom's printer, a 100 miles away, after enabling the *VLAN* associated with the EoIP tunnel in mDNS in /ip/dns... I can printer a web page on my Mom's inkjet. Without repeating mDNS, the printer would not show up as an option in the Print Dialog. After it I pick the HP in the dropdown.

With the new mDNS Proxy feature, I should just be able to add the 2 VLAN interfaces I want to broadcast between in IP/DNS and it should work correct? I had communication between my phone and Google Nests work with PIM for ages and for some reason it just stopped working so I want to give mDNS a try