Automate default DNS record provisioning for new cPanel accounts and domains using custom zone blueprints.
If you manage several domains or hosting accounts, DNS templates can simplify your administration while helping ensure every new domain starts with the correct DNS configuration. By creating a DNS template, you can automatically apply standard DNS records whenever new hosting accounts or domains are created. This saves time, improves consistency, and reduces manual configuration across multiple websites. This guide will help you create and customise a DNS template in WHM for your 1-grid VPS or Dedicated Server.
Before You Begin
Before creating or editing a DNS template, ensure that you meet the following baseline criteria:
- You have Root or Reseller privileges on your 1-grid VPS or Dedicated Server.
- An active server management dashboard with access to WHM functions.
- A clear blueprint of the required custom zones and a firm understanding of basic DNS syntax.
💡 Context: A DNS template is a predefined set of zones that WHM references whenever a new cPanel workspace or domain mapping initialises. Defining default layouts once eliminates the need to manually build standard records (A, CNAME, MX, or TXT verification blocks) for every new customer asset.
Follow These Steps
1. Log in to WHM
Log in to WHM to initialise your root control interface.
2. Open DNS Zone Templates
Locate the navigation search bar in the top-left sidebar panel layout. Type “Edit Zone Templates” into the search field row, then click the link matching that description under the DNS Functions section block cluster panel.
3. Choose the Template to Edit
The WHM platform renders three baseline default DNS template configurations:
standardvirtualhost– Recommended. The core framework file referenced whenever standard new cPanel accounts or add-on domains are built.standardvirtualftp– The configuration file used specifically when generating secondary FTP domain tracking aliases.standardvirtualmac– A legacy environment template file utilised for specialised Macintosh server profile routing.- Action: Click on the standardvirtualhost text link to open the raw template text window layout.
4. Modify the DNS Template Code
Inside the editor text frame layout, add, rewrite, or update your default record strings. You can declare specific variables (such as %ip% or %domain%) to ensure WHM scales the strings dynamically based on the account details. Review your template to ensure proper formatting for common zones:
- A Records: Maps your root host entries back to your primary web server destination IPv4 string.
- CNAME Records: Deploys unified alias links for common prefixes (e.g., mapping
wwwback to the root). - MX Records: Assigns mail server routing targets for mail delivery systems.
- TXT Records: Pushes mandatory structural verification text fields such as default SPF, DKIM, or DMARC authentication strings to protect your clients from email spoofing.
5. Save the Template
Scroll to the absolute bottom of the template layout dashboard and click the Save action button. The interface will refresh with a confirmation alert indicating that the zone profile is successfully modified.
6. Test Your DNS Template
To confirm your automated templates run correctly, navigate to Account Functions → Create a New Account and spin up a lightweight test cPanel domain. Once the initialisation loop finishes, open Edit DNS Zone under DNS Functions, select your test target domain, and verify that all customised template entries are generated automatically.
What Happens Next?
Once the template file writes to the system configuration disk sector, changes apply to future automation queues.
- Frictionless Onboarding: Adding a sub-domain or client site instantly populates your exact, validated mail infrastructure pointers and server IP targets.
- Isolation of Legacy Records: Note that structural adjustments apply strictly to new domain initialisations; existing, active DNS zones running on your server remain completely untouched.
Important Things to Know
- Syntax Vulnerabilities: Errant periods or missing character spaces within your zone records can crash your server’s local BIND DNS service completely, taking all automated sub-zones offline. Cross-check your formatting before saving.
- Propagation Boundaries: Newly built zones are still subject to standard regional internet service provider network DNS propagation delays of up to 24 hours when launched onto live registration routes.
Common Mistakes to Avoid
- Misunderstanding template scopes and assuming your changes will retroactively rewrite records on your existing, active client domains.
- Inputting typos or invalid characters into highly sensitive zone records.
- Failing to capture a baseline text copy backup of your factory template layout before typing modifications.
- Overlooking the required trailing period punctuation rule required by absolute domain designations inside server zone files.
- Pushing incorrect, dynamic, or unverified server destination IP variables inside your master A Record rows.
If This Didn’t Work
Should newly built hosting accounts fail to populate your custom DNS layouts, verify that you applied your changes to the true standardvirtualhost template path row rather than alternative mac files. If your zone creation tool outputs critical BIND compilation error logs, restore your plain factory backup script code lines to re-establish a clear system operational baseline.
You’re Ready!
Your WHM custom DNS zone configuration templates are fully deployed on your 1-grid server node. Automating your DNS blueprints eliminates repetitive admin tasks and ensures every new web asset initialises with a secure baseline configuration.
Related Articles
- Manage DNS Zones in WHM
- Understanding DNS Records (A, MX, CNAME and TXT)
- How DNS Propagation Works
- How SPF and DKIM Improve Email Delivery with 1-grid
Need Help?
If your template dashboard drops modifications with system execution blocks, or if newly generated sub-zones trigger lookup errors that stall your web deployments, contact us. Our Support Team is ready to provide guidance and support.
Before logging an architectural ticket request, please prepare:
- Your primary server hostname and client account profile details.
- A copy-text clip or screenshot of your modified DNS template file view.
- A screen capture of the resulting broken DNS zone table generated for a test account.
- The complete text configuration of any error messages displayed inside the WHM status frame.