Additional Domains / Aliases

Use Sites → Settings → Additional Domains / Aliases when the same Herne site should answer for more than one hostname.

• Use the www alias switch on General for the primary domain's own www host.
• Use Additional Domains / Aliases for other hostnames such as alternate domains, campaign domains, or temporary migration domains.
• Use Canonical Domain Migration when the primary domain itself must be renamed and files should move to a new canonical path.

• Add opens a modal for the hostname, redirect mode, SSL inclusion, and notes.
• Edit opens the same modal with the current values.
• Delete uses a destructive confirmation modal before removing the hostname.
• The table keeps compact row actions and badges for active, redirect, and SSL behavior.

Aliases share the existing site's project root and document root. Herne updates the generated Nginx config so active serving aliases appear in server_name.

• Aliases marked Redirect to primary receive redirect behavior instead of directly serving the app.
• Aliases marked Include in SSL are included when SSL is enabled or re-synced.
• External DNS is supported; the alias does not require a Herne-managed DNS zone.
• A mismatched A record remains a blocking DNS problem, while migrated apex NS warnings can be non-blocking for known external zones.

Use External Site Redirect when the primary site should permanently send visitors to a different HTTP or HTTPS origin, including a site managed by another Herne Panel server.

• Keep the source domain DNS pointed at the source server so it can answer the request.
• Keep source SSL enabled so HTTPS requests can be accepted before the redirect.
• Enter an origin such as https://play.fklavye.net. Herne generates HTTP 301 blocks for the primary domain, www, and active aliases.
• The original path and query string are preserved; /games?id=12 redirects to the same path and query on the destination.
• Clear the destination field and save to restore normal site serving.

CMS and other multi-site applications should use normal site aliases too. Add each hostname under Additional Domains / Aliases and keep Redirect to primary disabled so every hostname serves the same app root.

The application can then resolve the correct internal site from the request domain. Herne only manages the hosting layer: Nginx server_name, SSL coverage, logs, runtime settings, and the shared document root.