@kanchil 

If you can ping hostnames of windows machines, there is a local dns working on your LAN.

What does the dns entry look like in your ethernet/wifi  properties?

Have you tried manually configuring the dns server field to your router's LAN IP address and see if that works?

  @kanchil Hello, please see these google search results that explain why customers have been requesting (for many years) tp-link to add a local DNS server to the routers.

https://www.google.com/search?hl=en&as_q=local+dns+hostnames&as_epq=tp-link

As mentioned, this problem affects non-Windows machines the most - IP cameras, NAS, linux machines, etc.

Windows machines have their own proprietary Microsoft method for resolving hostnames on the LAN.  Thanks.

  @kanchil 

Did you notice the DNS server entries in my screenshot were the local router? That is "obtain dns server automatically" set.

So what does the be3600 do for you in windows when your network interface is set to automatically obtain the DNS server information?

Again, have you tried manually entering your routers IP address in the DNS server field in Linux?

  @kanchil Thanks for your reply.  Yes, my tp-link router DNS works fine for public addresses and local Windows machines.  But I cannot ping/resolve hostnames for local IoT, ipcam, linux and other non-windows machines.

ping cnn(dot)com  [works]
ping microsoft(dot)com  [works]

ping win-pc1.local  [works]

ping win-pc2  [works]

ping ipcam1.local  [host not found]

ping sys-linux2  [host not found]

With other routers like ASUS, Netgear, OpenWRT, etc. the ping to ipcam1.local and sys-linux2 works successfully, since they have an internal DNS server.

Unfortunately tp-link router does not have an internal DNS server.

  @kanchil 

What does your DNS server entry on your network interface on Windows say when you have it set to "obtain DNS addressing automatically" in the ipv4 properties?

If it says your routers ip, then you have a  local dns.

In my case, my be800 has local DNS. Sounds like something may be wrong with how some of your devices on your lan are receiving DNS information.

  @kanchil I just found this thread below. Any new news about this feature request?  Hope the BE3600 will get this "internal DNS server" enhancement.  Thanks.

"This feature request about adding the local DNS server to Omada Router has already been submitted to the developer team for evaluation, it's planned to add the support in the future firmware updates"

https://community.tp-link.com/en/business/forum/topic/542472

  @kanchil 

If you're not going to check what I mentioned about your DNs server information in windows (similar to the screenshot I posted), then good luck to you in not realizing you may already have local DNS..

Also, omada is enterprise which means that usually DNS is handled by IT that knows how to setup a separate DNS server (the more that is segregated the less chance for taking down other vital network services on the same server).

So it's not surprising it doesnt have local DNS by default, where home consumer routers usually do since the average home user is not aware of how to setup a separate DNS server (which the be3600 is targeted for).

  @kanchil sorry, the screen shot is below.  the automatically acquired DNS server is 192.168.0.1

In this old thread from 2021 the tp-link tech knows about the lack of an internal DNS server in the router

"Hi @sureshredis, I didn't make myself clear in my previous reply. The TP-Link router doesn't support resolve the *** local hostnames ***  via DNS, it doesn’t support ping hostname either."

https://community.tp-link.com/en/home/forum/topic/500282

*deleted screenshot*

  @kanchil 

I recommend removing your IPv6 public address and MAC address (or any public network information) anytime you post a network information screenshot on the internet as it is a security risk.

Since the automatically acquired dns server IP address is your router IP address, your router is acting as your local DNS server.

The be3600 is not 3 years old so the thread you linked does not apply to this newer be3600 router.

If you are using device isolation under advanced > Security, that may be why they cannot be pinged as well.

  @kanchil The Device Isolation is OFF.  Thanks, i've deleted the screenshot with the ipv6 address.

All the hostnames on the local LAN are visible in Network Map -> Clients.  But Ping to non-windows-hostname gets host not found.  Ping to non-windows-ip-address works fine.

Really hope the internal DNS server feature is done quickly for the Omada line, and is propagated to the consumer, Archer routers.  Any news?

Another thread this year August, about "Deco doesn't support resolving the local hostname to the IP address"

https://community.tp-link.com/en/home/forum/topic/684922