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 tabs depending on the module config.
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, it will show the domain's nameserver status. If the domain isn't set to the default nameserver for the module, then a notification will be shown to the client and allowing them to Switch Nameserver to the default nameservers.
The client will have the ability to Reset the domain back to original state
The client will have the ability to clear all the DNS records under the zone. Leaving all the email forward, catch-all, redirect intact.
DNS Templates (Professional Edition Only)
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 may choose the Preserve my currentDNSrecords option to keep it's current DNS records in the zone during a template restore.
Dynamic DNS API / DynDNS (Professional Edition Only)
This option allows for the client to automatically update it's A record using a remote API call, similar to many DDNS provider.
Special note: If the client has multiple A record, the module will only update the 1st one it finds.
DNS Zone Editor
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.
NS records, the module is designed to not allow 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.
Web Redirect (Premium/Pro Edition Only)
The client will be able to manage the web redirection using this tab.
Email Forwarding (Premium/Pro Edition Only)
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. An email will then be send to the email destination inbox with a verification pin to allow for the client to verify the email destination.
The email client won't be able to assign the Email Destination to a Forwarding Alias 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.