4
Votes

LAN DNS entries from DHCP Leases

 
4
Votes

LAN DNS entries from DHCP Leases

LAN DNS entries from DHCP Leases
LAN DNS entries from DHCP Leases
2026-03-19 08:32:59
Tags: #DNS
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.3.3

Model: ER605-M2  

Hardware Version: V2

Firmware Version: 2.3.3

 

Improve the use of the LAN-DNS by automatically or easy manual import of DHCP-Leases into the LAN-DNS

 

User-Story: 

I have around 200 Network-Devices in my Home-Lab local Lan and i want to use the Omada DHCP Service for the network.
It would be great to get all Leases fixed or temporary to show up in a local LAN-DNS.

 

Why?

This is a Standard-Feature of other Vendors (Cisco, Unify...)

 

Proposed Solution:

Activate DNS-Entry and Alias in the Client-Config: 

The Mockup shows

  • additional checkbox to enable the LAN-DNS-Entry for the Client
  • A Text-Field for a List of Domains the Client should be Associated with
  • A Text-Field for a List of Alias-Names in addition to the Client-Name

 

Why in the Clients-Config, not in the DHCP-Config?

  • Put into Clients-Config so it also available for Fixed IPs that have not been assigned by the DHCP
  • DHCP-Clients - update the DNS-Entries every time the Lease is renewed
#1
6 Reply
Re:LAN DNS entries from DHCP Leases
2026-03-25 11:44:04

Hi @tpriko,

 

I've tried to propose this back in June 2025, but the static entries only were marked as expected behavior..... see my old post here.

 

 

/BR ZoloNN ----------------------------------------------------------------------- Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0 CET (GMT+1)
#2
Re:LAN DNS entries from DHCP Leases
2026-03-25 12:33:57

  @ZoloNN i talked to the business-sales and they understood perfectly fine, that this would be a feature that would push the value of the devices and give them an edge on other vendors... but...

 

This is why i made a Feature Request and hope that the Developers will see it. 
There is actually a DIY solution for the self deployed omada-controller.

 

And since on a low level it is only a matter of synchronizing text-files this should not be hard to implement.

#3
Re:LAN DNS entries from DHCP Leases
2026-03-25 12:45:59

Hi @tpriko,

 

as I wrote in my original post, this is only a matter of changing two configuration files in the gateway which is described in following OpenWRT README. No change to the firmware build itself is necessary.

 

 

/BR ZoloNN ----------------------------------------------------------------------- Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0 CET (GMT+1)
#4
RE:LAN DNS entries from DHCP Leases
Yesterday
The lan dns was a great addition but connecting it to DHCP would allow me to to not run another dns server for this. If you need this functionality. The is a coredns plugin that does this
#5
Re:LAN DNS entries from DHCP Leases
Yesterday

  @ZoloNN how does that work on the hardware omada controller?

#6
Re:LAN DNS entries from DHCP Leases
13 hours ago

Hi @tpriko,

 

if you mean the @Broncosis usage of coredns plugin it should work with any version of Controller.

 

but if you're asking about the integration of dnsmasq and unbound - this is a question for tp-link as we (as users) don't have access to the corresponding config files on gateways....

all what is needed is a small change of two plain text text config files - for reference see my original post and you may vote for it

 

/BR ZoloNN ----------------------------------------------------------------------- Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0 CET (GMT+1)
#7