@userofarcherc80 

Hi,

There are routers on the market that do actually support such feature, but the one's from TP-Link apparently do not, at least not the models I own.

I think the next best thing you could do to be able to access your NAS via the name "nas" is to give the NAS a fixed IP address (preferably via the "Address Reservation" feature of the C80) and then add a corresponding entry to your PC's "hosts" file.

For example, if you permanently fix the IP address of your NAS to 192.168.1.103 and add the entry "192.168.1.103 NAS" to the "hosts" file of your PC, then you can access your NAS from that PC via the name "NAS". (like "ping nas" or "http://nas" or "\\nas"  in Windows Explorer)

In MS Windows the link to the hosts file is "C:\Windows\System32\drivers\etc\hosts" and in Unix-like operating systems it's "/etc/hosts".

Hi,

thx for a hint. I was hesitating to try it because

IMHO a static IP config and updating /etc/hosts

at all NAS clients is against the DHCP purpose

and the DNS purpose. 

So I have tried to disable DHCP server on Archer, in hope

upstream DHCP server on the fritz modem catches up, ...

well it bricked the Archer.

After Archer factory reset I have selected the access point mode

and it resolved the problem. There might be some downsides

but I have spotted just one so far, an access to admin console is

tricky (via mac address -1).

So it confirms that looking up DHCP Device Names via DNS

is possible and some other devices feature it by default.

(if Archer C80 features it, it's well-hidden somewhere).

There was a phase I tried that NAS advertises itself via

upnp and/or bonjour but there were always some clients

that could not understand it.

   Regards