You just need to specify the interface where mDNS should be “shared”.
/ip/dns set mdns-repeat-ifaces=vlan20,vlan10
There is no enable, just add the interfaces.
But “disable”… there is should be a “reset” in /ip/dns to do it, but isn’t. But using an empty string will “disable” it:
/ip/dns set mdns-repeat-ifaces=""
Had to revert to 16.2 due to WireGard not starting. It looked like Current Endpoint could not retrieve static DNS entries. Looking in the cache table the IP was present for the static DNS entry.
I had the same issue with WG DNS endpoints. Maybe this drop has the “overhauled” DNS?
Humm… A new feature, and it already comes without support to Interface-Lists.
“overhauled” DNS already makes me shiver…
Yeah, it looks like the people who managed the “refactored DNS service internal processes” didn’t carry out the most basic tests. It makes me wonder if they’re even conducting CI/CD pipeline test automation at all..
I would have cheered when the changelog line was “changed DNS resolver to unbound” but unfortunately that does not seem to be what is happening…
That resolver includes an elaborate regression test set and -tool in the source code. Those guys know why that is important for DNS resolvers…
And it seems like making /ip/dns VRF-aware in 7.15 according to https://download.mikrotik.com/routeros/7.15/CHANGELOG is still broken in 7.16beta3 
*) dns - added VRF support;
I am assuming that the mDNS feature requires that the Firewall allows inbound on all the relevant interfaces for udp port 5353 for IP packets addressed even if addressed to 224.0.0.251 ?
@Apachez are you the same Apachez on VYOS forum, if you are I’m glad you are here too
In other words, you’re dropping support for RFC 3056. Because that needs unspecified remote address. Is it intentional?
I know that the whole thing is not very popular. Accompanied RFC 3068 is even deprecated. I’m probably one of the few who still use it (not with v7, because attempting to do so crashes it; SUP-97719). I’ll (have to) survive without it, but I was hoping that you would eventually fix it, since you broke it (it works fine in Linux), and it might still be useful for someone.
Static DNS querying will be fixed in the upcoming RouterOS beta release. Please remember - this is beta. Released for testing new features and fixes. Some services might not work properly, and these version should not be used on important routers. As for the DoH - we are looking into this and will update later on.
In IPv6 my VLANs no longer show up dynamically under ND - only the bridge. Do I need to add them manually and the global addresses and routes? I moved from 7.15.2 stable to 7.16beta3.
I have had my issues where the /ip/dns VRF-awareness is failing for both the stable 7.15.1 and 7.15.2 aswell as the 7.16beta2 and 7.16beta3.
Dear MikroTik team, please do not take this negatively. This is well-intentioned advice. There is a quote that even beta releases are tested by thousands of automated tests (http://forum.mikrotik.com/t/qa-of-software-releases/176605/1). Then a beta version appears with a DoH that cannot work at all - due to a dead-lock situation (static DNS entries are ignored, but DoH domains must be resolved to IP). No one tested this - not even manually. And it is not that a bug occurred somewhere one would say: “woah, that is pretty weird that this change broke unrelated functionality X”. No, the feature in changelog itself was not working as intended. It would be so wise and positive to cover new features with corresponding tests! Software quality would increase dramatically! It is clear that it is almost impossible to retrospectively cover an entire ROS with automated tests; with all possible configuration options, it would be an absurd amount of effort, and probably not all cases would be covered still. But as mentioned: when adding new features, it is certainly advisable to have the basic functionality of the feature covered by a few tests.
Yup, thats me! (failed to find how to send you a DM so the reply is public instead).
This was brought up in a previous thread, but here is my proposal for formatting the change logs. Add and adjust headers as necessary.
7.16beta1 > (2024-06-05 11:52)
Changes
- supout > - added netwatch section
Fixes
- route > - fixed memory leak (introduced in v7.15);
This is a beta version, not a production version.
Using beta in production are just asking for trouble.
If you have error, report it and it many be fixed.
Yeah sure, but bugs in the DNS resolver are often complex and difficult to hunt down, I have already wasted way too much time on them.
I already made a mental note: skip 7.16 upgrades until at least 7.16.2 is released…
Yes that’s correct. If your firewall drops the udp multicasts on the input chain, the mDNS proxy will not see the traffic and thus does not repeat anything.