It's even more frustrating because when I brought it up with my solutions rep, they came up with all these other options that didn't solve the issue, and didn't really have much to say when I said "watch this" and shared my screen, pulled up the one single off-domain site that we have which uses Ubiquiti hardware, and there wasn't a single mDNS name anywhere. I showed him how I can instantly see exactly what every single device is at a quick glance. The response was "Yeah... that definitely seems like it might be helpful."   I honestly can't believe that THE networking company doesn't have a solution in place for this. ... 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

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