Count me in for 7206.

Seems like pretty basic stuff for "Enterprise" grade hardware.

For anyone looking for a workaround, you can use NextDNS and use the "Rewrite" feature to achieve similar results.

new update is out!

New update still no local DNS. Whole project blocked by this sh**. You CAN work around it, but you LOSE the whole purpose of why you EVEN BUY into it. Might as well go with anything else and DIY, which is what you usually do not want (and pay a premium to be everything omada compatible).

Already contacted TP-Link support, employee was completely incompetent, randomly referring pages in the manual for everything that has the word "DNS" in it. After 20mins of shooting me with this nonsense in the chat he finally got it. The asked me why anyone would need local DNS, why not set all static IPs. I asked politely to elevate the issue to someone else. Promised to reply, this was like 3 months ago, nothing heard. For anyone planning to buy into Omada, better don't. Buy something else before it is too late.

If you really want to have a local DNS, take 5 minutes of your time and leave a one star review on Amazon:
https://www.amazon.de/product-reviews/B08MH4VLR3/

That's where it hurts, support and this forum will ignore you.

jd001 wrote

The asked me why anyone would need local DNS, why not set all static IPs. 

And that is the real problem: TP-Link does not see that a local DNS is something that is needed. That's why this request has been open for so long and nothing has been done. It's technically not that difficult but TP-Link does NOT want to implement this because they think setting static IPs is good enough.

This is just not an acceptable solution in the year 2023 ... but TP-Link does not want to acknowledge that. I can only recommend for anyone still stuck on this to get out and buy a  modern networking solution. I myself switched over to Ubiquity gear and it all just works, including local DNS.

  @aschmid  It looks like we will still have to move our hotels to UniFi or Aruba, and there is an option to use local DNS. In addition, there is another reason, this is a richer functionality of client (host) settings . I understand that there is Omada Pro, but judging by the reviews and webinars. Many points are still missing, and even more in raw test form. And God knows when it will work stably and in full.

( Is it really so difficult to implement, Monitoring the traffic of hosts in real time. When you see traffic in the context of customers, and not...Total depersonalized traffic with a delay of several minutes )

  @Fae I don't get it that it takes so long... Dnsmasq is available in the router, but not configured properly? It could not be that hard?

If anyone is interested I am selling all my Omada stuff, just pm me. Less than a year old, will fo 30% off of whatever it costs new.

OC300
ER605v1
SG3428X
4x EAP215 WALL

Will also exchange for non TP-Link devices.