Good question. As everything was up to date on the "Firmware" screen, I have thinking yes. I double checked; the update of the controller is not there. From the settings, I am updating it now. It might be good to bring the controller update to the "firmware" tab as it is "central" place? After update: I still can't find the Lan DNS feature. Btw, the OC200 is much slower with the new firmware. Almost unusable. Way to slow to consider it acceptable. Thanks anyway for the idea..

  @MR.S , thanks

 

I found the setting under Settings → LAN → LAN DNS. However, I was surprised to see that this feature requires manual input. I expected clients to have some form of automated local DNS management.

 

Maintaining a local DNS app (adguard, pi-hole) with scripts is much faster if we can't leverage client data (such as name and IP) automatically.

 

Suggestion for the developers: Please consider an option to auto-populate LAN DNS with client_name.local configurations. This kind of automation would be highly beneficial when managing networks with 10, 100, or more clients.

 

Thanks!

  @YooCH 

 

Take a look at this Docker container: https://github.com/dougbw/coredns_omada

 

I've been wishing the Omada controller had this functionality built specifically for conditional forwarding from Pihole to resolve the friendly names I've given in Omada.  I just hate how long it took me to realize this even existed.  It works great!

 

There are a couple of caveats:

• If running on the same host as Pihole/Adguard or some other DNS service, it needs to be set it up using macvlan-net (to give it a unique "real" IP address on your network).
• There seems to be Docker limitations that an application running natively on the Doctor host can't talk to a Docker conteiner running as macvlan which was a problem in my case as my "backup" Pihole IS running natively on the same host as the Coredns_omada container.  I was able to work around this by pointing conditional forwarding on my "primary" Pihole (running on a different host) then pointing my backup Pihole conditional forwarding to the primary.  I suppose it could be possible to solve this my making the Pihole on that host a Docker container and also part of the macvlan-net but haven't tried that.

  @SingletrackMind

Thanks,

 

I saw that project and I even started to create my own code using omada API to get client list, then push it to Adguard instance I have.

I was not happy to run Adguard only for that, now I start using it to filter ads too. I might continue with my own code. I have a proxmox ruuning in my rack where I try many tools.

 

The Lan DNS could replace all this setup if it is done internally in the ER8411.

I already use DNS proxy (with external DNS ads filter - Cloudflare) and DNS cache from it.

Just need some automation to be happy.

 

I need to decide to continue to build internal services or keep simple setup with use most of Omada.