We have that set now in our environment - "Turn off multicast name resolution" to enabled, which has other security benefits.  Unfortunately, the damage is done for every system that previously connected to Meraki.  I've been manually updating names when I'm in there and looking for systems.  As a secondary request, it would be great to delete clients and let them get redetected so the name is correct.  I wouldn't mind loosing the client history if that were the tradeoff.  Thanks for your suggestions! ... View more

I'm also interested in a real response as to why this would be difficult to implement or why the mdns client name is some kind of benefit to me.   This design limitation really wrecks the "at-a-glance" nature of the interface. ... View more

I've set this setting in our Chrome interface and can now see Chromebooks in my dhcp interface with the meaningful name.  Meraki is still showing the meaningless mdns string and as of yet doesn't give us a way to change the naming priority of client devices. ... View more

Totally agree with this.  I'm not sure how having the device named with an mdns string is more convenient then having the host name as the client name in Meraki.  I also haven't seen a post explaining why it's a benefit to admins to have the naming order this way or why it's a hard-engineering problem to change it.  I'd be happy to show any Meraki engineer how this slows down our use of their system and ruins the "at-a-glance" nature of the interface.  ... View more

We can't identify devices.  I have to look at Meraki, then find the device IP, then look at DHCP and find the hostname.  If #4 were #2 on this list, the information would be dramatically more useful. ... View more