@dantana The best way, if we use Deco M9 as router, we need router features. Otherwise it is not useable.

In my case, Deco M9 are in bridge mode and a PfSense is the router. I didn't plan that, but nom it is like that...

man, here I was thinking my whole network somehow became misconfigured.

tplink please add local hostname resolution!

so frustrating.

So much for a router...

I just ran into this same issue on my x60, devices that advertise themselves with mDNS can be used by hostname, but that isn't the router resolving the hostname so you can't use something like nslookup and anything that doesn't know about mDNS (like an older device) won't resolve by hostname.

It's not a huge issue since most of the devices I would connect to / from do support mDNS, but a lot of smart devices don't even advertise themselves with anything besides registering with the local DNS, so I have a lot of unnecessaryIP reservations set up and have to remember which device has which IP.

This is a fairly major feature to be missing from a router as expensive as this though, every previous router I've owned has resolved local DNS hostnames and had a web interface for configuration instead of requiring an app.

I am assuming this is only the problem when Deco mesh runs in Router mode. For Deco in Access Point mode it would not be an issue.

You can put me down for wanting this too.  Some old devices on my network incorrectly expect that gateway can resolve dns requests.  What makes the lack of this feature even worse is that you can't turn DHCP off on Decos.  So, I can't add my own DHCP server (like a pi-hole) to resolve local dns requests.  One hack I've been using is append ".local" to hostnames.  I believe that uses Netbios to resolve the name instead of DNS.  I think this is the first router I've ever seen that doesn't support local dns caching.