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

  @Clive_A 

Hi Clive

Yes, sorry but you're confusing services. A .local resolution as you show is done with mDNS, which is not what we're talking about, as it doesn't work in some scenarios. We're asking about plain old DNS port 53 resolution.

  @Clive_A 

You're not giving any address right now, when using mDNS is the server or client computer the one that is answering the query, not the router. I'm pasting an image of my explanation as somehow the forum is giving me errors about external links.

Thanks!

  @Clive_A No, DNS entries for DHCP hosts was what everyone has been asking for the whole time. It seems like you and the team misunderstood, which makes sense if you weren't thinking about it because you thought mDNS already solved it. As others have pointed out, mDNS is not the same thing. The example you asked for is in my prior post. It should not require any config, unless you count a checkbox somewhere to enable or disable the behavior. An optional but strongly recommended config would be to set a domain name for the associated LAN, so that the DHCP hostnames can have an FQDN, and/or so that the gateway's DNS server can ignore and blindly forward requests that don't match the internal domain. Look to OpenWRT for inspiration on settings for this sort of thing.