This document outline the Client functions of the Module
For your clients to access the module, they can either go through the WHMCS Domains tab → DNS Manager or via domain details page → Side bar → Manage DNS Records, Email Forwarding & Redirect
Once entered, the module will ask for the client to select from the list of Active domains under the account to manage.
On the Index page, client may see 6 different tabls
Overview, DNS Zone Editor, Web Redirect, Email Forwarding, Email Catch-all & Notification. Each of these can be enable/disable in the Module config.
In the Overview tab will show the domain's nameserver status. If the domain isn't set to the default nameserver for the module, then a notice panel will show to the client telling them some and allowing them to Switch Nameserver.
The client will have the ability to Reset the domain back to original state by click on the Reset Domain button
The client will have the ability to clear all the DNS records under the zone, leaving all the email forward, catch-all, redirect in tact.
Depending on the module config, your client will be able to create it's own DNS template and/or restore from System DNS templates or it's own.
The client can choose the Preserve my current DNS records to keep it's current DNS records in the zone or override it when without.
This option allows for the client to automatically update it's A record using a remote API call, similar to many DynDNS provider.
Special note: If the client has multiple A record, the module will only update the 1st one it finds.
The client can modify and manage the domain's DNS zone within this tab. Each of the records (A, AAAA, CNAME, MX, TXT, SRV, NS) can be limited and enable/disabled individually based on your liking.
Regarding NS record, the module is designed to disallow clients to manually remove the NS record for the main domain. This is to prevent clients from accidentally removing the NS record causing the whole zone to fail.
The client will be able to manage the web redirection using this tab.
The client can manage the email forwarding in this tab. In order for the Email Forwarding to work, the client must first add an Email Destination. Once the Email Destination has been added, the client will receive an email containing a Pin to verify the destination.
The email client won't be able to assign the Email Destination to use with Forwarding unless the Destination has been verified.
When the client is ready to setup the Forwarding, they can simply use the Add Alias function to add a forwarding source. Once the alias as been added, they can now assign the Email Destination to the Alias.
The client will be able to set a catch-all address. Similar to Email Forwarding, the client must first have a verified Email Destination before they can assign to the catch-all.
The client can choose whether they want to accept email notification regarding changes made within this module.