Guys if you keep posting workarounds you are basically telling TP Link it's ok for them to take their time with this feature. Work arounds are not acceptable on enterprise grade solutions.

Everything is replaced and for sale now, located in Germany. Less than a year old, the wall APs are still in use but can be sold together. I am not waiting anymore for this cr4p.

Btw I figured you need to purchase the ER605 in order to have DHCP working with Omada. But when disassembling I figured the switch was still acting as the DHCP Server.. Scam. So you need to buy an additional router that technically does..nothing.

You can still use everthing properly outside of Omada, I decided to not buy TP Link anymore.

@KimcheeGUN 

That is not the point. I also use an external DNS server on my deployments. But the router, where the DHCP server resides, must still be able to resolve local names so the DNS server can query it. That is the whole point. Or else I must make a manual mapping on the DNS server to the local names and update it with any change.

I want to be able to connect to my local devices with names and not IP addresses and I want to use the router DHCP. For that to happen, the only way is for the router to have a built in DNS server that can resolve local hostnames.

Also, jd001 just pointed out the switch is able to act as a DHCP server. What does that have to do with the local DNS topic that warrants you to reply saying that this solution may not be for him? Any system admnistrator needs a local name resolver. That is a basic feature...

 @KimcheeGUN  I am an IT professional with more than 15 yrs of practical experience. Of course I know how to configure it properly, you just did not get the point at all.

In case of the DNS server, this might be true for huge companies, but Omada is explicitly marketed for use in small business, like hotels.

The DHCP server feature is marketed on the feature list of the managed switch, which is quite reasonable. The thing is, when all your devices are being managed via SDN, you cannot activate it UNLESS you buy a router, it is a software restriction. I did want to have the DHCP config within SDN (Omada), but I already had a cable router. Because of proprietary software restrictions of Omada I was forced to buy a router, obly to find out the switch acts as the DHCP server all on its own. So basically I was running a second router for no good reason.

  @jd001 

I'm curious to see if you can sell that stack of equipment, as I have the exact same stuff and more - for sale because TP-Link expensively (for us customers) totally missed the boat and seem totally unconcerned that they're still standing on an empty shore. Empty is what their customer list should be until they right such an egregious oversight.

I moved to Peplink and am curious what you used to replace your TP-Link gear. I've been well down the Ubiquiti road, and it was great at first... but later they seemed to care little to nothing about customer experience either from my perspective; especially when support was validly needed.

  @cgh001 I am a software developer and linux guy, so I took a Sophos SG and put latest OpenWRT on it (ER605 is based on an outdated version of OpenWRT..). Works like a charm, and since I have all devices integrated into one, it even consumes less power. The Sophos can be extended via flexible modules to 4x10Gbe SFP+ ports or more RJ45 ports if need be, which really is just PCI-Express in a weird mechanical constellation, so you can also buy cards from other manufacturers such as Checkpoint. I even upgraded the CPU so I have some additional hardware support for cryptography. Basically, it is just a plain PC in rack format. I am going to backup it using something like Veeam maybe, not sure yet.

For the WiFi, I am still searching, but I am going to take some standalone solution. Funny enough, now I could even run the Omada controller in software on my router to keep my TP-Link APs.