Review Webuzo Primary Domain and Nameserver Changes by Version

Changing a Webuzo primary-domain setting is distinct from registering a domain or updating its registrar nameservers. The correct controls depend on the installed Webuzo generation and your authorized role. Historical single-user Webuzo settings must not be assumed to describe every current multi-user account.

Preserve the current design

Record the actual primary domain, IP, nameservers and affected sites before changing anything. Preserve recoverable configuration, website, database and mail data privately. Review certificates, account associations, application URLs, DNS authority and panel access; changing a label does not update every dependency.

Legacy versus current controls

The historical guide used admin Settings/General > Webuzo Config. Webuzo’s v2 documentation also describes a nameserver/primary-IP/domain tab. If maintaining that release, inspect the exact supported fields and submit only the approved values. Do not alter the primary IP as a side effect of changing a domain.

For a current installation, use its supported administrator or domain-management controls for the intended task. A normal hosted-domain add/rename is not necessarily a server-level primary-domain change. If the UI or scope differs, obtain the release-specific procedure through the vendor or your support ticket rather than copying old configuration files.

Nameserver fields do not change delegation

Nameserver defaults still need an actual authoritative service, correct zones and required registrar host/glue registration. Changing them in a panel does not automatically alter every registered domain’s parent delegation. Review DNSSEC relationships before a planned DNS cutover.

The old free-license statement and CentOS 7 installation link are not current account or deployment guarantees. Confirm licensing and supported operating-system requirements for the actual service instead of relying on this historical settings guide.

Verify and retain rollback

Check panel access, authoritative answers, website/TLS, mail and application paths after any approved change. Keep the prior values and recovery route until all intended services are verified. Do not remove/re-add an active primary domain merely to trigger certificate or authentication initialization.

References: historical Webuzo nameserver/primary-domain settings and current domain-management topics.

Reviewed October 16, 2026. Historical controls are explicitly scoped; no primary-domain, IP, license or delegation change was performed.