Skip to Content
Browse documentation

UAPP Domains

Manage hosting-account domains in UAPP with scope, feature requirements, document roots, redirects, application selection and cache controls.

Open Hosting → Domains. These controls manage domain configuration for the signed-in hosting account.

MenuPurpose
All DomainsReview domain types, usage and shared website controls.
Addon DomainsAdd separate hosted domains and manage their document roots.
SubdomainsCreate names beneath an owned parent domain.
AliasesAdd names initially sharing the account's public_html content.
Domain App SelectorSelect an available website application configuration.
RedirectsManage destination, HTTPS and WWW redirection.
Cache PurgeRequest cache invalidation for a domain or URL.

Addon Domains, Subdomains, Aliases and Redirects require their individual account feature switches. Creation also checks the relevant plan allowance. All Domains, Domain App Selector and Cache Purge are direct menu entries; their actions still check domain ownership.

Document roots and domain identity

Document roots are entered relative to your account home, for example public_html/shop. Do not enter an absolute server path or URL. The form allows 1–253 word, dot, slash or hyphen characters, forbids a leading slash/dot and a trailing slash/dot. Use a normal path without traversal segments and keep private files outside served directories.

Domain fields accept validated domain names, including supported wildcard names and normalized internationalized names. Adding hosting configuration does not register a domain or change registrar delegation. Verify DNS, certificate coverage and the served website separately.

Treat submissions as live changes

The current domain views and their helpers have no explicit demo-mode write guard. Do not submit sample domains or changes merely to inspect a form. Preserve needed recovery data before deleting domains, removing files or switching website configuration.

Most configuration mutations record domain activity outcomes. Cache Purge does not record an explicit domain audit event in these views. A successful response is not an end-to-end website, DNS, SSL or cache test. If an operation fails, inspect the current domain list before retrying because configuration may already have been written.