Add a domain to the correct Webuzo hosting account before uploading its website. The domain definition connects a hostname to a document root and service settings; it does not register the domain or automatically change external authoritative DNS.
IN THIS ARTICLE
Check access and requirements
Confirm ownership of the domain, available account allowance and its intended website directory. Decide whether this is an independent addon website, a subdomain or an alias of existing content. Back up any directory that already contains files.
01 Add a domain and website in Webuzo
- In the end-user panel open Domains > Add Domain. Choose the domain type that matches the intended behaviour. An independent website should not accidentally share another site document root.
- Enter the hostname without a URL path. Review the proposed directory and avoid placing private application files in a publicly served root.
- Review automatic certificate and mail-validation options. Certificate issuance requires successful domain validation, while mail records must match the actual sender and mailbox provider.
- Save the domain and inspect it in Manage Domains. Upload a harmless test page to the recorded directory before deploying the full application.
- Publish the correct website A and, if used, AAAA records at the authoritative DNS provider. Test the host header against the destination before switching an existing production site.
- Choose the supported PHP version and install the application or upload its release. Configure HTTPS after the certificate is valid, then remove the temporary test file.
Does an alias create a separate website?
An alias normally presents an existing website under another hostname. Choose an addon domain with an appropriate separate directory when the site needs independent content.
Confirm the expected result
Load the exact domain over HTTPS and confirm it shows the intended account content. Test the www hostname separately if you intend to use it. Verify the certificate, application routing and a controlled database action rather than checking only that the panel lists the domain.
Resolve setup problems
If the wrong site appears, compare authoritative DNS, the selected document root and the domain type. If validation fails, inspect stale IPv6 records and proxy behaviour. Do not delete an existing domain with customer data just to retry its setup; correct the specific mapping.