Feature Request: Wildcard Domain Support in Load Balancer

[paulocastellano]

Summary:
I want to request support for wildcard domains (e.g., *.example.com) in the Load Balancer, which would allow dynamic routing of subdomains to our application servers without manually registering each subdomain.

Use case:
At changelogfy.com, we allow our users to host changelogs on custom subdomains such as customer1.changelogfy.com, customer2.changelogfy.com, and so on. These subdomains are generated dynamically and need to be routed by the Load Balancer to the appropriate backend service (PHP/Laravel-based).

Currently, without wildcard domain support, each subdomain must be manually configured on the Load Balancer, which is not scalable and adds significant operational overhead.

Expected Behavior:
The Load Balancer should:
• Accept *.changelogfy.com as a wildcard listener
• Route traffic based on wildcard hostname patterns
• Forward requests to the same pool of PHP servers

**User Request:**   customer1.changelogfy.com
                      │
                      ▼
            ┌────────────────────┐
            │   Load Balancer    │  ← should match wildcard `*.changelogfy.com`
            └────────┬───────────┘
                     │
          ┌──────────┴────────────┐
          │          │            │
          ▼          ▼            ▼
     PHP App 1   PHP App 2    PHP App 3   ← Laravel servers

Benefits:
• 🔁 Scales with customer growth
• 🛠️ Simplifies DevOps
• 🧩 Compatible with SaaS architectures
• 🧪 Makes local/staging environments easier to replicate

Please consider adding support for wildcard domains in Load Balancer configuration. It’s essential for any modern SaaS infrastructure.

We use Laravel Forge, and they support it.

[saeedvaziry]

I don't think this is related to the load balancer. This is simply the vhost configuration of the website and you need to do it only once.

You basically need to update the vhost config and accept wildcard