Your DNS service.Ready for every customer you choose.

Create eligibility rules around selected WHMCS products, purchased services, addons, domains or TLDs. Each rule can define when access begins, the number of domains allowed, where zones are placed and which records start the service. An eligibility preview helps you see how the rule applies.

Yes, when the selected offer permits them. The customer requests the domain through an eligible purchase, publishes the ownership challenge and follows verification. The workspace provides the DNS tools and nameserver guidance for the resulting service.

A template holds a reusable record set for an application, website or mail service. Values can come from the domain, hosting service, server, selected custom fields or customer input. You choose its audience and application behavior, and the resulting changes pass through review and history.

The platform profiles include cPanel/WHM, Cloudflare, BIND 9, PowerDNS, Plesk DNS, Route 53, Google Cloud DNS, Azure DNS, DigitalOcean, ClouDNS, Akamai/Linode, Vultr, Hetzner, NS1 and DNS Made Easy. The customer tools follow the capabilities of the selected connection and package.

Yes. When enabled in the customer policy, a reviewed change can be prepared for a future service cycle and cancelled before execution. Snapshots preserve earlier record sets, and the restore workflow lets the customer review a previous configuration against the current zone before applying it.

The cPanel hosting handoff coordinates a DNS-only zone with hosting account creation and termination. It preserves record state, uses the configured merge behavior and keeps transition results available for staff. Lifecycle settings also define retention, holds and cleanup as services change.

Yes. Start the seven-day free trial of DNS & Forwarding and explore the features through a workflow relevant to your business. The trial page explains the terms and starting steps. The annual licence is available when you decide to continue.

The current version is shown on this page, and the Changelog opens the release notes. Each published release explains its new capabilities, improvements and fixes. You can read the notes in the page or open the full release history when you want to follow the product over time.

Yes. With the forwarding gateway configured, web-forwarding rules can use permanent or temporary redirects and control whether the path and query string are preserved. Supported status choices include 301, 302, 307 and 308. The module checks conflicting web records and keeps the redirect connected to the DNS records needed to serve it.

The customer configures a domain-based alias and its receiving mailbox, with one destination per alias. Destination verification can be required before the route becomes active. The service checks for conflicting mail records and connects the forwarding rule to the required DNS setup, using the forwarding infrastructure and permissions you configure.

Yes. The customer workspace supports structured bulk changes and TTL work with a preview of the proposed record set. Protected records, service limits and available provider capabilities remain part of the operation. Staff can enable the appropriate tools through the customer policy, giving permitted users a clearer way to prepare a coordinated DNS update.

Yes. BIND and JSON imports can be reviewed as additions to the current records. When a full migration is intended, the import workflow also provides an explicit replacement option. Preview the differences before applying the record set, with protected-record preservation and the customer's effective policy remaining part of the process.

Yes, when exports are enabled for their service. The workspace can export BIND or JSON record sets for use outside the module. Snapshots and restoration provide a separate recovery workflow within the service, with customer backup limits and permissions set by your policy. Customers can therefore keep a portable record copy as well as use the recovery tools you offer.

Yes, where the selected provider and registrar support the required operations. Customers can view DNSSEC information and request the signing or DS changes available to their service. Your approval settings can require staff review before a request runs. The offered controls follow the service's capabilities and the customer's effective permissions.

The reverse-DNS workflow supports delegated IPv4 and IPv6 resources, with block registration and authority verification. Customer requests are checked against the relevant IP allocation and service policy, with optional forward matching and approval settings. This lets you offer PTR management for the address resources your service is entitled to control.

Yes. Start with global defaults, then apply customer or individual-domain overrides. You can tailor record types, TTL ranges, record and bulk limits, import, export, restoration, backups and scheduling. Staff can review the combined effective policy, while provider capabilities and the global service switches continue to determine which operations are available.

The inspection checks the live managed zone for duplicate records, conflicting or looping CNAMEs, inconsistent TTL values and common MX, SPF or DMARC configuration problems. Findings are grouped by severity and name. Support staff can use that detail to move from a broad customer report to the record set that needs review.

Yes. Nameserver and authority views show observed delegation and publication checks against the configured authoritative servers. Provider and synchronization status add context about the managed copies. Together, these views help staff investigate a migration or recent change and understand the relationship between stored records and the nameservers serving the domain.

Yes. A package can contain multiple connections with a selected management master and synchronized members. Staff control placement, provider pools and the capabilities each connection exposes, then follow synchronization for the individual targets. This supports a consistent customer workspace while keeping the underlying server arrangement visible to your operations team.

Yes. Existing-zone discovery searches connected backends, matches domains and tracks the discovered records. Zones are linked through explicit ownership and resource rules. Inventory onboarding can work progressively through an established WHMCS installation, helping staff bring eligible existing services into view under the provider and service configuration they have chosen.