Set up branded reseller nameservers

Reseller hosting clients on Gold and Titanium plans can present their own branded nameservers (e.g. ns1.youragency.com / ns2.youragency.com) instead of our generic ns21.canspace.ca style nameservers. Your sub-clients see your brand, not ours. This article covers what's needed and how to set it up.

What you'll need

1. A domain you control to brand the nameservers under (e.g. youragency.com).
2. Two nameserver hostnames you want to use (typically ns1.youragency.com and ns2.youragency.com, but you can pick any subdomains).
3. Glue records registered at the registrar where the brand domain is registered — we'll provide the IP addresses.

Step 1 — ask us for the IPs

Open a support ticket requesting branded nameservers. Tell us:

• Your reseller account / domain
• The two nameserver hostnames you want (e.g. ns1.youragency.com, ns2.youragency.com)
• The domain those hostnames are subdomains of (where the glue records will live)

We'll reply with two IP addresses — one for each nameserver hostname. These are real CanSpace nameserver IPs.

Step 2 — register glue records

Glue records are registered at the parent domain's registrar. They tell the world that ns1.youragency.com resolves to a specific IP, and they're stored in the TLD registry's parent zone (not in your domain's zone file).

If youragency.com is registered with CanSpace, just include the glue request in your same support ticket and we'll register them for you. If it's registered elsewhere, you'll need to register them yourself via that registrar's interface:

• GoDaddy: My Products → Domains → DNS → Host Names
• Namecheap: Domain List → Manage → Advanced DNS → Personal DNS Server
• Tucows / OpenSRS / etc.: search support docs for "register host" or "child nameserver"

For each, register the hostname (e.g. ns1.youragency.com) paired with the IP we provided.

For more on glue records, see Glue records.

Step 3 — we configure the WHM side

Reply to the ticket once your glue records are registered (and propagated — verify with dig ns1.youragency.com; you should get the IP back). We'll then:

1. Add your two nameserver hostnames to your WHM as the default nameservers for new accounts you create.
2. Configure DNS clustering so when you create a cPanel sub-account, its zone file gets pushed to both branded nameservers automatically (just like our regular setup).
3. Update the package defaults so new clients you provision are handed the branded nameservers in their welcome email.

Once we confirm completion (usually within one business day), your sub-clients will see ns1.youragency.com in their welcome emails and DNS configurations — no mention of CanSpace.

Day-to-day: assigning branded nameservers to a new client

Once branded NS are set up, every new cPanel account you create through WHM → Create a New Account will automatically use them. No further action needed per-account.

For existing accounts created before the change, you can update them via WHM → Account Functions → Modify an Account, but typically you'd leave existing accounts as-is and only roll out branded NS to new clients.

Updating clients' domain registrations

Your sub-clients still need to point their domains at ns1.youragency.com / ns2.youragency.com — either by registering the domain through you, or by setting nameservers manually at whatever registrar holds the domain. If you re-sell domain registrations through your own brand, you can ship them already pointed at your branded NS.

What if I want to brand reseller-of-reseller setups?

Branded NS only goes one level deep with our standard reseller plans. If you have a sub-reseller that wants their own branded NS, that requires more complex DNS clustering. Open a ticket and we'll discuss what's possible.

Related articles

• Glue records
• How do I log in to WHM?
• How do I create a new cPanel account?

Still stuck? Open a support ticket