This is ridiculous! We need factual information as to where this function is in the development queue NOT another rant from some forum moderator.

  @Ataboy (Probably my last ever post here... we'll see)

Honestly, while it's not graceful, and can seem expensive in the immediate, just do what I and others have done: Buy a different brand and don't look back. How much is managing attempted work-arounds costing in the long run (additional equipment, config, scripting/coding, management, etc.)? I'll bet it's far more than the price of a competitor's product that actually does what is needed to be done.

 

When enough customers defect the brand overall and it truly impacts tp-link's bottom line, changes will actually start to come to fruition. Whether they make it right with prior stranded customers will remain to be seen (low confidence there) but the only real language these companies speak is $. When people stop showing up and paying for their products, they'll then take notice. In my situation, tp-link is dead to me and I have no intention of ever purchasing any of their products again; due to how poorly this has been implemented, the gross lack of communication on the front end of the product's total inability to do (what most consider mandatory/required/assumed) basic needed functionality, as well as the "progress" toward a correction, and how said correction has been handled over the past several YEARS.

 

Like I said, it may not seem palpable in the moment but it will ultimately save lots of money, time and heartburn to simply defect and implement a different brand for infrastructure - especially when the alternatives actually already build-in mandatory expected features like local DNS resolution. FYI: Peplink is an excellent alternative, albeit significantly more pricey. But then again, the amount of time I've saved from switching to something that actually works as expected over the last year and a half has more than paid for the difference in equipment costs.

 

Good luck!

C

does the dev team have a jira tracking ticket open for this ?

 

the last decent update is from Jan here noting potential version numbers

 

wondering if anyone has tix open on this too />?

Lacking this feature is a real PITA for users. You've done a great job adding DNS proxy, DNS cache, etc. We're just missing this last piece of the DNS puzzle.

I've realized that selling all my Ubiquiti gear to switch to Omada (TP-Link) was a terrible idea. A product with this much potential requires users to implement their DNS, Pi-Hole, or Adguard form. Users can also not have local domain resolution or access a single device via an IP address. The fact that a thirty-dollar router or switching device has these capabilities built-in makes me wonder what is happening with this company. 

 

Can anyone recommend an alternative cloud-hosted or managed SD-WAN solution that supports 2.5g and 10G fast connectivity? 

  @ferrari2000 I moved to Peplink equipment myself and find it to be much better in general. It's more expensive, but as the saying goes: you get what you pay for.

 

And now, with the TP-Link router debacle with the US gov't, they'll be even more distracted from correcting such design flaws, elongating expectations even more for any hope of a fix. Plus, if there's merrit to the gov't concerns (not saying whether there is or not here,) probably best to move to a different brand anyway.

ferrari2000 wrote

I've realized that selling all my Ubiquiti gear to switch to Omada (TP-Link) was a terrible idea. A product with this much potential requires users to implement their DNS, Pi-Hole, or Adguard form. Users can also not have local domain resolution or access a single device via an IP address. The fact that a thirty-dollar router or switching device has these capabilities built-in makes me wonder what is happening with this company. 

 

Can anyone recommend an alternative cloud-hosted or managed SD-WAN solution that supports 2.5g and 10G fast connectivity? 

 

What is the tentative release date of the firmware?

Here, finally : https://community.tp-link.com/en/business/forum/topic/734414

 

6) Added support for LAN DNS in Site View > Settings > Wired & Wireless Network > LAN. This feature requires gateway's firmware to adapt to v5.15.

 

Don't pop the champagne yet. This feature is implemented at the router level, meaning a firmware update for the router is still needed.