Configuration Guide How to Configure Local DNS Server on Omada Router

Background:
This post provides a configuration guide on configuring the local DNS server in standalone mode.
This Article Applies to:
Omada routers with LAN DNS capability.
Configuration Steps:
1. Log in to your router by 192.168.0.1(default gateway IP).
2. Go to Network > LAN > LAN DNS. Click Add.
2. Create a DNS entry. Note that this DNS entry may apply to a single network or all of your VLAN interfaces.
Verification:
Open Command Prompt:
In this case, we are using .local and .com. You may use other suffixes.
In this case, the DNS server is 192.168.0.1. The resolution is 192.168.0.1. It is displayed as such.
Enter the domain names:
Note:
1. Configuration steps for Controller mode are similar.
2. Please note that this will involve an adapted firmware, not just a controller update. Firmware development is a complex process, and timelines may change. Therefore, we cannot provide a specific release date at this time. Please stay tuned to future firmware release notes for updates.
3. When introducing a feature like this, we typically apply it uniformly across all models to ensure consistency and a seamless user experience.
However, it's essential to acknowledge that hardware limitations may exist, which might prevent us from adding the feature to certain models. In such cases, we cannot provide individual notifications explaining the reason. Please note that we cannot guarantee the fulfillment of all requests, and we must set clear expectations upfront.
4. When the Type is IP/CNAME, wildcard * is supported. For example, "*.tplink.com" means that all domain names containing ".
tplink.com" are supported, but such as "tplink.*.com" or "
tplink.com.*” are not supported.
5. Please make sure your DNS server IP is the router's LAN IP. Or this Local DNS server(LAN DNS) configuration is not effective.
6. VPN would be effective for the local DNS configuration. Make sure you have configured the VPN server DNS as the router's LAN IP.
Update Log:
Feb 11th, 2025:
Release of the article.
Recommended Threads:
How to Disable NAT on Omada Router
Differences Between Router and Switch
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Feedback:
- If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
- If there is anything unclear in this solution post, please feel free to comment below.
Thank you in advance for your valuable feedback!
------------------------------------------------------------------------------------------------
Have other off-topic issues to report?
Welcome to > Start a New Thread < and elaborate on the issue for assistance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
arrmo wrote
@Clive_A OK, that does make sense - sadly. But ... I just want to be able to access local machines, by name (and local domain, so FQDN). This is not possible, nor planned? Thinking if dnsmasq (or similar, Unbind, or another) is running locally - it's quite simple to enable this functionality, really just about configuration of the DHCP server (and DNS server ... the same LOL).
Am I able to SSH in to my router / gateway, to try to configure this? Happy to help debug it. It's really pretty basic (and simple ;)).
Thanks!
Configure the LAN DNS, then.
It is only static, not dynamic, like what you expected it to be. It does not mean this thing is not working at all.
I don't know what you're talking about. Why does the subject suddenly become a troubleshooting?
- Copy Link
- Report Inappropriate Content
@Clive_A Sorry, trying to get it working dynamic. I had assumed all along that "LAN DNS" would be as I have seen on OpenWrt before (as I have built and used it on several routers and WAP's in the past). I have almost 60 clients on the network, so manual entry is a real pain ... I'm perhaps better to reinstall CoreDNS, but I had hoped to get rid of that, just use the router for DHCP and DNS.
And sorry, I wasn't trying to turn this into debug - was just hoping to use DNS so I could try to get it working dynamic (as I do know it works ... I have used dnsmasq and Unbind both, on OpenWrt based devices).
Thanks.
- Copy Link
- Report Inappropriate Content
Hi @arrmo
Thanks for posting in our business forum.
arrmo wrote
@Clive_A Sorry, trying to get it working dynamic. I had assumed all along that "LAN DNS" would be as I have seen on OpenWrt before (as I have built and used it on several routers and WAP's in the past). I have almost 60 clients on the network, so manual entry is a real pain ... I'm perhaps better to reinstall CoreDNS, but I had hoped to get rid of that, just use the router for DHCP and DNS.
And sorry, I wasn't trying to turn this into debug - was just hoping to use DNS so I could try to get it working dynamic (as I do know it works ... I have used dnsmasq and Unbind both, on OpenWrt based devices).
Thanks.
Yes. This is static instead of dynamic, which indicates that you have no workarounds or options to do a dynamic with this feature now.
Like I wrote, someone has reported this earlier. I sent it to the dev and see if they have any interest in adding that.
- Copy Link
- Report Inappropriate Content
Hmm. The announcement here says wildcards are supported, but when I try to use one it just tells me to enter a valid domain name:
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Clive_A any chance this is coming to ER7206 v1.0?
- Copy Link
- Report Inappropriate Content
Im wondering the same think!
Its pretty frustrating with the hw versions, in my as long as the product not eol. You would assume that different hw versions would have the same features or it should have different model number.
Kind regards, Niklas
- Copy Link
- Report Inappropriate Content
Clive_A wrote
Your first post states this. Note 4.
4. When the Type is IP/CNAME, wildcard * is supported. For example, "*.tplink.com" means that all domain names containing ".
tplink.com" are supported, but such as "tplink.*.com" or "
tplink.com.*” are not supported.
Same problem when trying to add a CNAME wildcard.
- Copy Link
- Report Inappropriate Content
bloblob wrote
Clive_A wrote
Your first post states this. Note 4.
4. When the Type is IP/CNAME, wildcard * is supported. For example, "*.
tplink.com" means that all domain names containing ".
tplink.com" are supported, but such as "tplink.*.com" or "
tplink.com.*” are not supported.
Same problem when trying to add a CNAME wildcard.
That note was written in the standalone mode. I believe the controller might not support it yet. Wait for the controller update.
- Copy Link
- Report Inappropriate Content
Is the LAN DNS static? So I have to add all clients manually? I have to use fixed IP addresses? Will there be dynamic DNS? All other routers i did have in all the years resolve the hostname based on the IP address that was given from the DHCP-server from the router. I use no fixed IP-addresses, fixed DNS doesn't work for me then?!
We have asked LAN DNS for a long time! My expectations where all the time that there will be dynamic DNS, like other routers. I hope that dynamic DNS will come also!
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 6619
Replies: 46
Voters 0
No one has voted for it yet.