A domain alias makes an additional domain serve the selected website while allowing that hostname to remain in the browser. The application can still impose its own canonical-domain redirect, so panel aliasing and application URL behavior must agree.
IN THIS ARTICLE
Check access and requirements
Control the additional domain and confirm it is not configured elsewhere in the account. Check your plan allowance, choose the target domain and plan DNS and certificate coverage. Consider whether a redirect would be more appropriate when only one public canonical address is desired.
01 Add a domain alias in DirectAdmin
- Select the intended website domain in DirectAdmin.
- Open Account Manager > Domain Pointers and choose Create Domain Pointer.
- Enter the additional domain as the source and select Create as an Alias. Review the name carefully before creation.
- Configure the alias DNS to the assigned hosting destination and arrange a TLS certificate covering the additional hostname. Aliasing does not by itself update a registrar or an external DNS provider.
- Review the website application settings. Some applications bind themselves to one site URL, cookie domain or allowed-host list and need an intentional configuration change before an alias is useful.
How do I verify the domain alias serves the right site?
Visit the alias over HTTPS and check the address bar, links, login flow and assets. Test forms and cookies in a fresh session, and confirm the main domain still functions. Review canonical URLs if search indexing matters to the site.
Resolve setup problems
If the browser changes to the main domain, inspect application or CDN redirects before assuming the alias failed. If HTTPS errors occur, correct certificate coverage. Do not use an alias to take over a domain you do not control, and do not change the main application URL without a recovery plan.