Does Front Door origins support wildcard hosts?

John 20 Reputation points
2024-08-13T20:09:04.7933333+00:00

I have an AKS cluster behind a Front Door, connected through a private link that is pointing to an internal load balancer. The cluster hosts multiple applications that are accessible through dynamically created subdomains.

My setup is as follows:

  1. My DNS forwards all requests to *.example.com to Front Door
  2. A route sends all requests for *.example.com to the cluster origin
  3. The cluster origin host name is set to example.com (with PLS enabled)

I am struggling to find out in 3. if its possible to use a wildcard host (*.example.com). This would essentially route requests for *.example.com to a single host. The requests would then be resolved by my ingress controller (so the original host name must be preserved up to this point), using the subdomain to route the request to the correct application.

Is this possible?

Azure Front Door
Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
668 questions
Azure
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
1,176 questions
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,073 questions
{count} votes

Accepted answer
  1. Rohith Vinnakota 315 Reputation points Microsoft Vendor
    2024-08-22T06:25:59.1466667+00:00

    Hi John,

    Thank you for reaching out to us on the Microsoft Q&A forum.

    As an original poster cannot accept their own answer, I am reposting it so that you can accept it an answer. Accepted answer will help other community members navigate to the appropriate solutions.

    Issue: Does Front Door origins support wildcard hosts?

    Solution: Setting a dummy subdomain in the origin host forwards the original host in the request to the origin. What I wanted was to set the origin host name to something like *.example.com, which is not possible, but x.example.com (or any string before .example) works. I also set the origin host header to blank.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. John 20 Reputation points
    2024-08-14T12:44:24.95+00:00

    I believe I have solved this.

    Setting a dummy subdomain in the origin host forwards the original host in the request to the origin. What i wanted was to set the origin host name to something like *.example.com, which is not possible, but x.example.com (or any string before .example) works. I also set the origin host header to blank.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.