Preconditions: You cannot manage custom nameservers via cPanel's Zone Editor as this feature is available only to customers with WHM "root" or "reseller" access. If you are using a shared hosting service/package and need this, please contact the WebHostingM support team for a fast upgrade.

For cPanel "root" admins, ensure that you have enabled this feature that allows resellers to manage nameserver records using the Edit Reseller Nameservers and Privileges > Nameserver Configuration.

Step 1: Create A Records for Your Nameservers

How to Configure Custom Nameservers with cPanel Reseller Privileges

 

  1. Log in to your cPanel account.
  2. Open the Zone Editor from the Domains section.
  3. Click Manage for the domain used in your custom nameservers.
  4. Click + Add Record.
  5. Create two A Records:
    • ns1.example_domain.com → 192.0.2.1
    • ns2.example_domain.com → 192.0.2.2

        # Verify your A records are properly set up with this command
        $ dig ns1.example_domain.com A
        $ dig ns2.example_domain.com A
    

Note: Replace 192.0.2.1 and 192.0.2.2 with your actual server IP addresses. If you have a shared IP, you may use the same IP for both nameservers, though some registrars require different IP addresses for each nameserver.

Step 2: Configure Nameservers in WHM

  1. Now log in to your WHM account.
  2. Scroll down to Nameserver Configuration from WHM » Home » Server Configuration » Basic WebHost Manager Setup.
  3. At the bottom of the page, you'll find nameserver entry fields.
  4. Enter your custom nameservers:
    • Nameserver 1: ns1.example_domain.com
    • Nameserver 2: ns2.example_domain.com
  5. Click Save Changes.

Step 3: Register Nameservers with Your Domain Registrar

You must register these nameservers with your domain registrar by creating "glue records." This process varies by registrar but generally includes:

  1. Log in to your domain registrar account.
  2. Look for "Register Nameservers," "Host Records," or "DNS Management."
  3. Add your nameserver hostnames and their corresponding IP addresses:
    • ns1.example_domain.com → 192.0.2.1
    • ns2.example_domain.com → 192.0.2.2
  4. Save your changes.

Important: Creating glue records at your registrar is a critical step. Without this, your custom nameservers will not function properly, as the parent DNS servers need to know where to find your nameservers.

Step 4: Configure Default Nameservers for Reseller Accounts

To set these custom nameservers as the default for all new accounts you create:

  1. In WHM, go to Reseller Center » Edit Reseller Nameservers and Privileges.
  2. Select your reseller account.
  3. Scroll to the Nameservers section.
  4. Select Explicitly Set the Nameservers.
  5. Enter your custom nameservers.
  6. Click Save Changes.

Note: This will only set the default nameservers for newly created accounts. Existing accounts will need to be updated manually or by the end users through their domain registrars.

Step 5: Wait for DNS Propagation

  1. Wait for DNS propagation (usually 1–24 hours).
  2. Verify your nameserver configuration using DNS lookup tools.

        # Verify your nameservers are properly set up and responding
        $ dig NS example_domain.com
        $ whois example_domain.com | grep "Name Server"
    

Common Issues and Troubleshooting

Nameserver Not Recognized by Registrar

If you receive an error like "nameservers not recognized" when trying to change your domain's nameservers:

  • Verify you've created the glue records at your registrar
  • Check that the A records for your nameservers exist in your DNS zone
  • Ensure the IP addresses match between your glue records and A records

Registrars Requiring Different IPs

Some registrars require different IP addresses for each nameserver, even if you're on a shared hosting plan with only one IP. Options include:

  • Contact WebHostingM's technical support team for additional IPs
  • Consider using the default nameservers provided by WebHostingM
  • Switch to a registrar that allows the same IP for multiple nameservers

Lame Delegation Errors

If DNS tools show "lame delegation" errors:

  • Ensure the NS records in your DNS zone match the nameservers registered at your domain registrar
  • Verify that your nameservers are responding authoritatively for your domain
  • Check that all DNS configurations match across your domain registrar and hosting provider

Important Notes

  • Access Requirements: This procedure requires reseller or root-level access in WHM. Regular cPanel users cannot configure custom nameservers.
  • Domain Ownership: You must own the domain you plan to use for your nameservers.
  • Propagation Time: DNS changes can take up to 24-48 hours to propagate worldwide.
  • Existing Accounts: Changes to default nameservers only affect newly created accounts, not existing ones.
  • Nameserver Changes: When changing nameservers for a domain, temporary downtime may occur during propagation.

Benefits of Custom Nameservers for Resellers

  • Branding: Your customers will see your domain in their DNS settings, enhancing your professional image
  • Independence: Domain migrations become easier if you need to change hosting providers
  • Consistency: All your customer domains can use the same nameservers across multiple reseller accounts
  • Control: You have more direct control over DNS management for your clients

Skip the DNS Configuration Hassle

We provide custom-built cPanel & WHM virtual machines, VPS, and bare-metal solutions hosted on Google Cloud, AWS, or OCI, specifically designed for businesses, organizations, and enterprises.

Instead of spending valuable time configuring DNS settings, contact us for a free consultation at talktous@webhostingm.net.

Our team of experts will help you set up a perfectly configured hosting environment tailored to your specific needs.

Did this answer help? 0 People found this helpful (0 Votes)