Accepted Add local DNS server to ER605
Please add a local DNS server, like dnsmasq, to the ER605. It's a bug for a business router that's running DHCP to not be able to resolve local host names.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
This request was posted over a year and a half ago and this past January you led us to believe you were working on an implementation for Local DNS server.
Now in June you give us this post that basically says -- "we recommend exploring alternative solutions that may meet your needs."
TPLink NEEDS to either say we are not going to do or MUST commit to a date you are going to deliver.
I deployed 7 ER7206's last May and now I see this TPLink post from June.
PLEASE NOTE: I am asking for this on the ER7206
- Copy Link
- Report Inappropriate Content
Yes, not having local DNS server has made me regret getting into the Omada ecosystem. I just can't return all my stuff now.
- Copy Link
- Report Inappropriate Content
Please add this to ER8411 as well.
- Copy Link
- Report Inappropriate Content
This request was posted over a year and a half ago and this past January you led us to believe you were working on an implementation for Local DNS server.
Now in June you give us this post that basically says -- "we recommend exploring alternative solutions that may meet your needs."
TPLink NEEDS to either say we are not going to do or MUST commit to a date you are going to deliver.
@Fae This, and exactly this.
Please provide us some more details.
- Copy Link
- Report Inappropriate Content
I don't know if I have to laugh or cry to see such a basic request takes so much time to be implemented !
And thinking that we are supposed to be on a business community forum only makes it more laughable.
No seriously, even domestic FAI box have this functionality, I really wonder who is Omada Solution for ???
Does the request made in this forum seriously be taken into account ? I start to think no.
If Omada program is given up, let us know quickly. Such a pity, on the outside Omada seemed amazing, but in reality, it's an empty shell...
- Copy Link
- Report Inappropriate Content
+1
- Copy Link
- Report Inappropriate Content
@hammer86 OK, perhaps a dumb comment, but what the heck ... LOL.
It seems that the router runs a VERY old version of OpenWrt. Why not get that current (23.05?), and allow ssh access? Adding a DNS package on top is trivial ... could likely even be done with the very old version of OpenWrt that is in use - so is the blocker the SDN / Controller? Perhaps do this in a 2 step way?
Thoughts?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 264
Views: 110224
Replies: 361