@M_Escaria 

M_Escaria wrote

  @Clive_A 

No wonder the users in the original ER605 thread were rude to you. Are you an official TP Link employee? If so, it simply shows the sub par quality of the company given the type of replies that you post.

 

I've been following this local DNS topic for the ER605 since the beggining and I decided to create an account just to point out the freak show this has been. The original post was created 3 years ago with the ER605 in mind. After 3 years of waiting for a feature that any 20$ router ships with from the factory, you post saying that the feature will only be implemented for the newers routers. This shows the utmost disrespect for customers. And I understand that being the face to this charade is not easy, but you had to expect some very dissatisfied customers who would just snap.

Also, your previous response to another user where you say, quote: " IT IS NOT. Geez... ....  If you have a grudge on this request, return or refund. " I mean, is this the official response from a TP-Link community manager? It's laughable at this point.

 

My advice: You are not qualified to deal with people. Has you also suggested at some point in one of the threads, find a job that suits you.

 

As for TP-Link, this is just one more topic in a very big list of amateur dealings.

Did you read the whole discussion in which I explained the situation?

And read what they said to me when I was patiently explaining the things and the situation? Did you see my work behind in pushing this?

If you don't, who/what gives you the right to judge me?

 

Bear in mind, I am allowed not to reply. But I want to be transparent. That's why everyone who replied in the 605 was replied to. But you guys don't seem to understand me. 

I am totally fine with my mouth shut. I can simply not share any information or let you know about the recent updates.

Department manager has discussed with me that "sometimes you don't have to be transparent and reply to everyone. Don't even reply to them. That's acceptable for your duty". Yeah, I think I don't have to bother you and get involved in some discussions now. If you need an apology, I am truly sorry for any information or comments from me.

 

TBH, I am starting to think that I am just giving too much attention to this matter or your opinions. There is no need to explain unnecessary stuff, and no need to try to be transparent and informative.

I am only doing the job holding my faith and what I believe should be right.

 

Without any grudge or emotions:

If this product fails to meet your expectations, please consider an alternative and proper solution ASAP to meet your needs. 

This is a template we use. If something cannot be done right now, and you need it right now, why do we have to argue over this? Get your network goal done quickly instead of wasting your time on this. What's wrong with it? You know it's 5 years, but it was only reviewed by the PM around 2 years ago.

 

If the product is subpar, please do consider upgrading your gears to something better and fancier.

Omada was only five years old and has developed fast in the last 2 years. I have been here with it for 5 years. I was doing this job because I could help people understand and share information. I might need a different job. Thanks for the suggestions.

And I should not force you to use something in your opinion that is below average. Right? I am giving you suggestions instead of controlling you to use subpar products.

 

In the end, wish you good luck building your network.  

I'll see other opportunities and get the manager to hire some new faces for this job. Thanks for the suggestions.

And a sincere apology for any comments that I have made.

  @Clive_A 

While I admit my own frustration with this topic too more importantly your reply has reminded me of a utmost certain fact: at every user name and post is a real person.    I do sincerely appreciate your posts and help.  
 

Also noted in this day of ultra sanitary over scrubbed non personal manicured replies by garbage by many, I find it refreshing to know there is a real person on the other side of @Clive_A    
 

Please ensure your manager knows many of us see the value in your time spent and help - please ask them to review this post.  

  @Screen1name 

totally agree!!

and i also think the function is essential to get the lineup of TP-Link from "good product" to "perfect fit", so we should not bring too much personal feeling into the backlog ;)

I think you guys are missing the point.

 

Clive_A I know you are just doing your job but you must understand that everyone that comments on these types of posts is a customer. And a customer will always demand the best value for his/her money. About this specific topic of the DNS server, you must understand that this is considered a basic feature. To have a router that doesn't resolve hostnames is like a car that has no interior lights for example. Sure, it still runs fine and takes you from A to B, but would it make sense that you had no interior lightning?

 

Anyway, the main point is that, at some point during the 3 years that passed since the ER605 post was created, the feature was tagged as accepted and that it would be implemented. There was an expectation that this basic feature would be implemented. After that, you guys came back on your word and said that it won't be anymore, only for newer routers. So, if you want the feature, you need to pay for a more expensive product and throw yours in the trash. Can't you see how bad this is? If I have to explain this basic stuff it means you don't know anything about customer relationships. It's as simple as that.

 

For my clients, they don't care if they have to spend 70$ or 300$ or 1000$ on a router. I had to implement work arounds to resolve hostnames that can be removed once you release this feature for the targeted routers. But this is not always the case. Some clients bought ER605 because it's more than enough for their needs and they'll be missing a critical feature. 

 

No one is looking for apologies (at least I'm certainly not). I just think that the backlash is more than warranted and you should not be surprised by it.

A much indeed needed feature. apparently this is meant to be an out of box ready feature.

i talked to the austrian business-sales team about it and they understood how this feature would make sense, after i showed them how easy this is on the unify-platform.
they also first thought about using the DNS-Cache for this. 

 

i also got the info out of them, that the dns even on the more expensive routers only offers manual dns entries.

for the selfhosted omada-controller version there is a git-repo. the "hack" reads out the dhcp every x minutes and augemnts the static dns with the etries...

 

nothing new from that front, but maybe now there will also be a feature request from within TP-Link

Maybe more of us should contact the local business-sales-teams....

 

 

  @Clive_A 

 

Hi, is ".internal" going to be supported? Any timeframe? Thanks

  @echamakiotis 

echamakiotis wrote

  @Clive_A 

 

Hi, is ".internal" going to be supported? Any timeframe? Thanks

The forum team does not provide information in reply about the development progress or details. 
Neither do we provide the estimated time for this feature, nor details and explanations for the roadmap. 

As this is an ongoing request and was previously replied to, your request is already known to the dev team.
Please refer to the final firmware release notes for this feature. 
Thanks for your understanding. 

basis