3
Votes

Support for Wildcard DNS Entries in Omada LAN DNS

 
3
Votes

Support for Wildcard DNS Entries in Omada LAN DNS

Support for Wildcard DNS Entries in Omada LAN DNS
Support for Wildcard DNS Entries in Omada LAN DNS
Tuesday - last edited Tuesday

At present, Omada does not allow adding wildcard domain entries (e.g., *<dot>example<dot>com) to the LAN DNS configuration.

 

Proposed Enhancement:
Enable support for wildcard DNS records in the LAN DNS settings. This would allow administrators to resolve all subdomains under a given domain (e.g., dev<dot>example<dot>com, test<dot>example<dot>com, api<dot>example<dot>com) without needing to create individual entries for each.

 

Benefits for Enterprise Customers:

  • Simplified Management: Reduces administrative overhead by eliminating the need to manually configure multiple subdomains.

  • Scalability: Ideal for large enterprise networks or dynamic environments where new subdomains are frequently created (e.g., staging, development, or containerized systems).

  • Consistency: Ensures uniform DNS resolution across all internal systems, minimizing configuration drift.

  • Time Efficiency: Speeds up onboarding and deployment processes for new services and hosts under the same domain.

  • Improved Flexibility: Supports modern application architectures, such as microservices or dynamically scaled infrastructure, that rely heavily on subdomain-based routing.

 

 

Doc about setting up LAN DNS: https://www.tp-link.com/us/support/faq/4504/

#1
Options
2 Reply
Re:Support for Wildcard DNS Entries in Omada LAN DNS
Thursday

  @gautamkrishnar 

 

Hello, thank you for posting on the TP-Link community. We appreciate all your feedback and feature requests here. While we don't have any specific details to share regarding

 

I'll ensure that I log this feature request and pass it along to the team.
Feel free to let us know of any other feature requests you may have; we’d be happy to send them up for you.

#2
Options
Re:Support for Wildcard DNS Entries in Omada LAN DNS
23 hours ago

@gautamkrishnar agree, LAN-DNS is an awesome addition and something many had been asking for! The per-network option is excellent too.

 

I immediately ran into a couple limitations:

  1. I could not FORWORD a wildcard to e.g. FORWARD '*<dot>acme<dot>com' to '1<dot>2<dot>3<dot>4'
  2. I could not FORWORD to an IPv6 DNS server address e.g. FORWARD '*<dot>com' to '2606:4700:4700::64'

 

Ideally the proposed wildcard will match as per rfc1034 / rc4592, so e.g. '*<dot>example<dot>com' will forward 'a<dot>b<dot>example<dot>com'.

 

We would like to move to IPv6-only networking ASAP, for that to happen, we need vendors like TP-Link to never add features that lack IPv6 support. Failing to consider IPv6 is regressive for the whole Internet.

#3
Options