Support for Wildcard DNS Entries in Omada LAN DNS
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/