[Feature Request] Support Multiple Domains per Resource with Primary Domain Redirect Option

[mgasche]

It would be very useful to have the ability to assign multiple domains to a single resource in Pangolin.

Currently, a resource seems to be tied to a single domain.
This limits flexibility when a service should be accessible via multiple domains or subdomains.

---

Proposed Feature

Add support for specifying multiple domains for a given resource, along with a setting to determine how Pangolin should handle requests to these domains.

Two modes could be available:

1. Primary Domain Redirect Mode

   • One domain is marked as the primary.
   • All requests to any other assigned domain are redirected to the primary domain via HTTP 301 (permanent redirect).
   • Ensures canonical URLs and SEO consistency.

2. Multi-Domain Mode

   • All assigned domains serve the same resource directly.
   • No redirects are performed; each domain remains independently accessible.

---

Benefits

• SEO control: Primary domain redirection prevents duplicate content issues.
• Brand flexibility: Serve content under multiple brand domains without creating duplicate configurations.
• Simplified configuration: Manage all domains for a resource in one place rather than duplicating resources.
• Subdomain preference: Especially useful for cases like example.ch and www.example.ch, allowing one of them to be declared as the primary domain while redirecting the other.

[Pallavikumarimdb]

This is similar to the request in #906 (2.2 Multiple Hostnames for a Single Resource).
I’m already working on that issue, so this feature will be addressed as part of that implementation.

[eggman9713]

This will be very useful for applications where I can only configure one domain for a resource on a client but it needs to function both inside the network and outside. For resource.domain.com, a local DNS record will capture that request and reroute it back inside the network but it will work through Pangolin on the outside. If I need to go from inside the network through Pangolin and back (usually just for testing purposes), using a subdomain like remote.resource.domain.com that local DNS won't capture will be excellent.

[github-actions[bot]]

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

[miloschwartz]

Thanks, converting this to a discussion thread so others can upvote and participate!

[kugelzucker]

id like that! now i have to create a source for everything on its own but if its a greeter page for instance i want to run a single nginx container and point multiple domains to it.

[paradizelost]

Definitely looking to have that here, i've got domain.example and www.domain.example that i need to go to the same back-end resource but need 2 resources to handle that today.

[thutex]

just updated to the latest release, and was sad to see that this still doesn't seem possible (though a lot of good work has been going on i see!)

i do hope this will become possible soon, because right now i either have multiple resources for the same thing (which makes no sense), a site that gives a 404 if you don't use www, or mess around with the traefik config to redirect non-www domains to www forcibly directly from the traefik configs, which isn't a perfect solution either