@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?

  @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? 

look! i've done it

https://community.tp-link.com/en/business/forum/topic/771322

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 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?

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

  @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".

  @Clive_A 

i want to say, yes, even business-customers are "spoiled" by upiquiti and cisco and others...

looking at the tp-link website i see the routers to be described with "enjoy", "easy", "convenient", "one-click..."...

so, what everybody wants is a local DNS-Function is:

• that gives us the ability to confgure fixed entries
• all the DHCP-Leases are automatically in there for fixed dhcp adresses
• all the dynamic DHCP-Leases 

  @Clive_A Hi Clive

I guess we're confusing terms here, nobody is asking for dynamic DNS (although that would be a nice addition).

There are two use cases that people is asking the local DNS for:

- Static DNS entries: so that we can set a record for "printer.lan" or "server1.lan" that the LAN clients can ask for and get their address.

- DHCP lease mapping: where the DHCP server mantains the DNS internal domain with the DHCP Host names that either the user's computers send or the fixed IP leases have configured, so that when Pete's computer gets an address we can refer to it as "petes-computer.lan"
 

And yes, we know about mDNS, but there are some situations where it's not working.

This is absolute basic functionality that every one other router brand have from the first day. The solution of installing a separate internal DNS server just to resolve IP addresses for a file server is, although working, too much of a hassle and a red line when reccommending gear to SMBs.

Add local DNS to a ER7212PC and that would be a PERFECT router for SMB installations.

  @Clive_A Yes I tested it... I wouldn't be here asking about it if it worked. I have never been able to resolve hostnames of my DHCP-assigned machines with Omada gear, neither before nor after this update. Are you sure you're talking about the same thing?

To be clear: My ER8411 is 192.168.1.1, which is adopted by my OC200 (192.168.1.2). I have no other VLANs besides the default. I boot a machine with hostname "host1" and obtain a DHCP lease for 192.168.1.114. Then from another machine, I run "dig @192.168.1.1 host1" and get no results.  I would like to see an A record pointing to 192.168.1.114. This is what nearly every router on the market has done for at least the last decade (usually because everything uses dnsmasq, and this is dnsmasq's default behavior).