@hammer86 Hello, yes I did set the "Primary DNS" field in my DHCP server to point to my local DNS server. But it did not resolve. 

I used another router, an ERLite-3 Router, immediately set it up and it works like a charm. Sucks to see that a TPLink router which cost $144 in my country doesnt have basic SMB  features like CLI, local DNS forwarder. Very dissappointed

  @cdx969696 @hammer86

Guys can you even read ? This thread is about a DNS server embedded in the OMADA router, so take your questions elsewhere (on how to configure external DNS address).

Hello @Fae 

could you tell us if there is any progress regarding local dns. (in reference to https://community.tp-link.com/en/business/forum/topic/546202 post #3)

Thanks and Greetings

@Fae +1 for the update.

I ended up running pihole as DHCP server, which is just absurd considering I spent over 500$ in enterprise level equipement.

It saddens me, but if TP Link does not care about this I'll be forced to switch to Unifi.

EDIT

@btx

I don't use cloud services so that's not really a problem.

It's true that you overpay in Unifi but at least you get a system with all the basics implemented.

And since when is this off topic? TP Link is failing to provide a base functionality and ignoring everyone that is asking for it so why would you not look at alternatives?

Can we get feedback from someone at TP-Link about this please?

I cannot believe a company this size would release a router designed for SME and Home/Office Environments without local DNS capabilities.

Surely it doesnt take much to add this feature!