@tpriko 

tpriko wrote

 

So the recommended solution is to buy the ER8411?

 

Or is this just for the 8411 the recommended solution and ER707-M2 Customers need to wait?

 

I dont get why filling the DHCP list of current leases into the DNS cache is complicated?

IT IS NOT. Geez...

This is to inform the 8411 users. "ONLY" is to remind people who do not read and think this is for 707-M2. Yes, there are people reading it is ER8411 but keep asking 707-M2.

Argh... I have explained many times that this is informative for the users who have ER8411. I have iterated so many times over when proposing a request, making sure they are separate. 

If you have a grudge on this request, return or refund.

I will remove any informative replies in case this is causing confusion.

Hi @kemurphy 

kemurphy wrote

  @Clive_A I see the feature available in both ER8411 and OC200 EA firmware, and I see the LAN DNS configuration screen now.  It looks like all we can do is list static DNS records for the LAN DNS to serve. However, the whole point of the request going back to the ER605 thread was to dynamically provide records (presumably A records, but maybe also PTR records) for DHCP clients, and I appear to still be unable to resolve those names even after the firmware upgrades.  Is there something I'm missing? Can we get some documentation on this?

Go to the Router page. Click Configuration Guide and pick the label DNS. You will find:

I keep updating guides and please use the function or search bar to search.

Also, encourage you to use the official website to find guides.

Hi @tpriko 

tpriko wrote

  @Clive_A 

look, i am not angry or something. 
if it is available in ER8411 now, is this a sign, it will come for the ER707-m2 too?

if this is a different beast and should be adressed in a separate ticket, just say so... ticket subject allures to expect both to be adressed in one?

 

you know i use tp-link privately. in my dayjob i build the local internet. i am used to work with developers, integrators and supplyers of network equipment.

if this is a thing that should be threated as a separate request, why not just create it? 

 

 

You don't know how frustrated I am. It feels like you are nitpicking.

In ER605, the very first thread requesting the DNS. Someone from that post is being extremely rude and ignorant by repeatedly asking me why it has not become available for ER605 V1 V2 right here right now.

I don't know if you read that thread or not. But I have explained not less than 10 times what's going on with this project and what I am trying to push this. No one appreciates what I do. I have been thinking I should leave this job or switch to a different team. No one really cares what I do for the community by writing guides and explaining how things work.

I explained. He kept asking the same over and over again and attacked me with slurs.

I posted that now some models are getting updates with the LAN DNS. He came and kept asking again why it is not available for ER605 V1 and questioned me what problem I have with posting other models information on LAN DNS in that thread instead of staying on the topic with ER605. 

That'll be fine. I don't reply to any other information in that thread. If you have a specific model for a specific feature, create a new one.

I now start to think it should be deleted if two models are involved in one request. It is not proper to do.

You replied like how he nitpicking. I am being informative to inform people that there are 8411 available for this feature. You came and questioned me why it is not available for 707-M2 right now.

See? Why I am frustrated? I started to think I didn't have to reply when a new firmware came out to support a feature. What I have done is to make trouble for myself and be questioned. Pre-release or Beta for different models is always not released at the same time. Dev got a schedule and orders for the models. When it has been released, a major update will come for all models to adapt to the new controller.

I try not to use AI to create replies and read everyone's posts. But it only hurts me. I should be robotic instead of being too passionate. In today's world, nobody cares about being hardworking and careful.

  @kemurphy

kemurphy wrote

Clive_A wrote

Hi @kemurphy 

kemurphy wrote

  @Clive_A I see the feature available in both ER8411 and OC200 EA firmware, and I see the LAN DNS configuration screen now.  It looks like all we can do is list static DNS records for the LAN DNS to serve. However, the whole point of the request going back to the ER605 thread was to dynamically provide records (presumably A records, but maybe also PTR records) for DHCP clients, and I appear to still be unable to resolve those names even after the firmware upgrades.  Is there something I'm missing? Can we get some documentation on this?

Go to the Router page. Click Configuration Guide and pick the label DNS. You will find:

 

 

I keep updating guides and please use the function or search bar to search.

Also, encourage you to use the official website to find guides.

  @Clive_A Thanks for the link. It would be great if these pages were discoverable somehow through the router's online manual or the product support page or the controller web UI.

 

However, your docs seem to confirm that the only supported feature is very limited static record configuration, and that there is still no support for resolving names of DHCP clients. Is that correct? If so, is that planned, and is the initial release here just an MVP?

Did you literally test it? It can resolve the hostname even before the LAN DNS is released. And if you are talking about the inter-VLAN hostname, that's mDNS.

There is no plan about what you are referring to because it's already there.

If you need that in the manual, wait for the docs team to update it. It may take quarters to do and revise the manuals. I personally wrote the guides for the community members in case they didn't know how to use them. It is not part of my job or mandatory for me.

  @bryan065 

bryan065 wrote

It would be nice to have both static records and dynamic DNS records like most other basic routers have.... Having to run a separate DNS server to resolve DHCP hostnames is a bummer...

 

707-M2 running the software controller

Not sure what you are talking about. Hostname is supported, did you test it? 

What does it have anything to do with the LAN DNS? What kind of documents do you refer to to get this conclusion?

If you need "dynamic DNS", you fill out the DNS server option in the LAN settings instead of using the router LAN DNS as a standalone function.

Clearly, if you want to build yourself a DNS server, you maintain it. That's how a business router with LAN DNS is meant to be. Spoiled by stuff like Adguard or Pi-hole? That's not how things work. Note that what we do is fundamental and essential for a business user.

You might consider using the DNS from the public providers if you need "dynamic DNS".