What Is Reseller Hosting and How Does It Work?

Overview

Reseller hosting is a hosting model where you purchase a block of server resources — disk space, bandwidth, RAM — from a provider like Host & Tech, then divide and sell that capacity to your own customers as if it were your own hosting service. You’re not managing the physical hardware. The provider handles the infrastructure; you manage the client accounts on top of it.

It’s most commonly used by web designers, developers, and digital agencies who host multiple client sites and want a single billing and management interface instead of juggling separate accounts. It’s also the starting point for anyone building a hosting business without the capital to buy and colocate their own servers.

The white label aspect is what makes reseller hosting commercially useful: your clients see your brand, your custom nameservers, and your support contact — not the underlying provider’s. From their perspective, you are the hosting company.

Prerequisites

• A reseller hosting plan (see Reseller Hosting plans at Host & Tech)
• Access to WHM (Web Host Manager) — this is the reseller control panel, separate from cPanel
• A domain name for your custom nameservers (e.g., ns1.yourbrand.com, ns2.yourbrand.com) if you want full white label branding
• Basic understanding of DNS — you’ll need to create A records pointing your nameservers to your reseller server’s IP
• Optionally: WHMCS or another billing platform if you plan to automate client invoicing and account provisioning

How Reseller Hosting Actually Works

The Two-Layer Control Panel Structure

This is where most beginners get confused. Reseller hosting uses two separate control panels:

• WHM (Web Host Manager) — your admin panel. You create and manage client accounts here, set resource limits, configure nameservers, and handle server-level settings.
• cPanel — your clients’ panel. Each account you create in WHM gets its own cPanel login. Clients use cPanel to manage email, files, databases, and domains — just like any standard cPanel hosting account.

You log into WHM at https://yourserver.hostandtech.com:2087 (or your custom domain once nameservers are configured). Your clients log into their cPanel at https://theirdomain.com:2083.

Packages and Resource Allocation

Inside WHM, you create “packages” — predefined resource limits you assign when creating a client account. A package might be:

• 10 GB disk space
• 100 GB monthly bandwidth
• 10 email accounts
• 5 MySQL databases
• Unlimited subdomains

You can create as many packages as you want and assign different ones to different clients. A small blog client gets your basic package; a WooCommerce store gets your business package. You’re slicing up your total reseller allocation however you see fit.

📝 Note: You can only allocate what you’ve actually purchased. If your reseller plan includes 100 GB total disk space and you’ve already assigned 90 GB across client packages, you have 10 GB left. Overselling is technically possible in WHM (there’s a toggle), but I’d strongly recommend leaving it off until you understand your actual usage patterns.

White Label Setup: Custom Nameservers

The white label part requires a small but important DNS step. To hide Host & Tech’s branding from your clients, you register private nameservers under your own domain and point them to your reseller server’s IP address.

Example: if your brand is FastSiteHost, you’d create:

ns1.fastsitehost.com  →  [your reseller server IP]
ns2.fastsitehost.com  →  [your reseller server IP]

You do this in two places:

1. At your domain registrar — register ns1 and ns2 as “glue records” (sometimes called “child nameservers”) pointing to your reseller IP. The exact UI varies by registrar — look for “Private Nameservers” or “Host Records” in your domain management panel.
2. In WHM — go to Server Configuration > Basic WebHost Manager Setup and enter your nameservers there so WHM uses them for all new accounts.

⚠ Warning: DNS changes take time to propagate — anywhere from a few minutes to 48 hours depending on TTL settings and your client’s ISP. Don’t create client accounts before your nameservers are resolving correctly or you’ll end up troubleshooting DNS issues that are really just propagation lag.

Creating a Client Account

Once your packages are set up, creating a client account takes about 60 seconds:

1. In WHM, go to Account Functions > Create a New Account
2. Enter the client’s domain name, desired cPanel username, password, and email address
3. Select the package you want to assign
4. Click Create

WHM creates the account, sets up the home directory at /home/username/, configures DNS zones, and provisions cPanel access automatically. You then send the client their cPanel login URL and credentials.

📝 Note: If you’re using WHMCS with the WHM/cPanel API, this entire process — account creation, welcome email, and billing setup — can be automated when a client completes checkout. That’s the standard setup for anyone running a real hosting business rather than manually managing a handful of client sites.

What You Don’t Control

It’s worth being upfront about the limitations. As a reseller, you don’t have root access to the server. You can’t install server-level software, modify PHP configurations beyond what WHM exposes, or change Apache/Nginx settings at the httpd.conf level. If a client needs something that requires root — say, a custom PHP extension that isn’t already installed — you’d need to raise a support ticket with Host & Tech.

If root access is a hard requirement for your clients, that’s when you’d look at a VPS or dedicated server instead. Our VPS plans start at $5.83/mo and give you full root access with your choice of control panel.

Common Issues & Troubleshooting

Nameservers Not Resolving After Setup

Symptom: You set up custom nameservers but client domains aren’t resolving, or WHM is still showing the provider’s default nameservers.

Cause: Usually either the glue records weren’t saved correctly at the registrar, or propagation is still in progress. Occasionally it’s because WHM’s Basic Setup wasn’t saved after entering the nameserver details.

Fix: Use a tool like dig ns1.yourdomain.com @8.8.8.8 to check if the A record is resolving from an external perspective. If it returns your server IP, the records are set — wait for propagation. If it returns nothing or the wrong IP, go back to your registrar and verify the glue records. Also double-check WHM under Server Configuration > Basic WebHost Manager Setup and hit Save again even if it looks correct.

Account Suspended Immediately After Creation

Symptom: A newly created client account shows as suspended in WHM right away.

Cause: You’ve hit your reseller plan’s account limit or total disk/bandwidth quota. WHM creates the account but immediately suspends it when it detects the overage.

Fix: Go to Account Information > List Accounts in WHM and check the total allocated resources. If you’ve reached your plan’s ceiling, you’ll need to upgrade your reseller plan or delete unused accounts before creating new ones.

Client Can’t Log Into cPanel

Symptom: Client reports they can’t reach their cPanel login page or get an “Unable to connect” error.

Cause: Most often, port 2083 is being blocked by the client’s firewall or ISP. Less commonly, the account is suspended or the domain hasn’t propagated yet.

Fix: Tell the client to try accessing cPanel via the direct IP: https://[server-ip]:2083. If that works, it’s a DNS issue. If it doesn’t, check in WHM that the account isn’t suspended. You can also provide the client with a direct cPanel login URL that bypasses their domain entirely — WHM’s List Accounts page has a cPanel icon next to each account that logs you in directly without needing the domain to resolve.

WHM Showing “Disk Usage Inconsistency” Warning

Symptom: WHM flags a disk inconsistency, and the usage numbers in account details don’t match what du reports on disk.

Cause: cPanel’s disk usage cache is stale. This happens after large file operations or when a lot of accounts are updated simultaneously.

Fix: In WHM, go to Server Configuration > Statistics Software Configuration and run a disk usage recalculation. Alternatively, if you have support access, ask Host & Tech to run quota -u username server-side to get the accurate figure. This is an annoyingly common quirk in cPanel environments and doesn’t usually indicate a real problem.

FAQ