Host Additional Domains on an Eligible InterServer Account

An InterServer hosting account can host additional names where its actual package and panel permissions allow it. Check the service’s domain, storage, inode, database, mail and resource limits first. An alias/domain pointer and a separate website are not necessarily the same feature.

Choose the relationship

For another independent website, use a separate intended content directory. For a second name showing the same site, use the panel’s alias/shared-content feature deliberately. Adding a name does not grant a separate pool of server resources, independent account isolation or universal full email service. Confirm mail and other entitlements for the exact plan through the authenticated account or support ticket.

Prepare account access and DNS

Sign in to the customer portal and open the actual web-hosting service. Use its assigned panel login and DNS instructions. Historical portal labels and placement may differ. Preserve the previous DNS and required mail/verification records before a cutover.

Provision the intended site and review its records before changing public traffic where the provider’s workflow permits. If pre-cutover domain validation blocks creation, request scoped help rather than enabling server-wide domain exceptions. External authoritative DNS can be valid; using InterServer hosting does not require blindly replacing every existing DNS service.

cPanel separate-site setup

Open Domains > Create a New Domain, enter the intended name and choose the supported independent-root option rather than sharing the main root. Review generated fields and submit. The cPanel domain guide explains management and removal scope. A successful save does not by itself install an application or obtain a trusted certificate.

DirectAdmin separate-site setup

Under the intended user, open Account Manager > Domain Setup > Add New where offered, enter the name, review actual limits/options and create it. Do not confuse adding a domain with creating a new panel user. See DirectAdmin domain management.

Verify each intended service

Deploy the correct content, check authoritative DNS and exact HTTPS hostname, and test relevant routes and separately provisioned mail. Keep unrelated domains untouched and preserve recovery copies before cleanup. DNS caches and application setup are separate; there is no fixed delay after which a blank site must be working.

References: cPanel domain relationships and DirectAdmin user-level domains.

Reviewed October 16, 2026. The matching multiple-domain FAQ was consolidated here. No plan entitlement, authenticated account walkthrough or customer site setup was independently tested.