Latest revision as of 12:51, 19 April 2024

DNS Manager V3 For WHMCS requires an active DNS Manager For WHMCS.
You must keep both addons active to be able to use the newest version of DNS Manager module in full.

[edit] About DNS Manager V3 For WHMCS

DNS Manager V3 For WHMCS is an end-to-end module that enables your customers to be in charge of their DNS zones.

Thanks to a wide variety of submodules, combined with options allowing you to prepare ready packages, your DNS Manager For WHMCS is there for you to surely meet your expectations.
As an administrator you have full control over DNS zones and possess access to a broad range of management options.

Wiki of DNS Manager For WHMCS 2.x can be found here.

Admin Area Features:

✔ Define DNS Servers

✔ Define Packages

✔ Create DNS Zones

✔ View And Edit Existing Zones

✔ Add And View DNS Slave Zones

✔ Lock/Unlock Zones From Edition By Clients

✔ Migrate Zones Between Chosen Servers

✔ Import Zones From Chosen Server

✔ Export Zone To TXT File In BIND Format

✔ Auto-Synchronize Zones And DNS Records Between Multiple Servers

✔ Manage Zones Backups

✔ Define, Manage And Duplicate DNS Records Set

✔ Apply DNS Record Sets To Multiple Zones At Once

✔ Wipe Existing Zone Records Upon Applying DNS Records Set

✔ Set Up Automated Tasks And Execution Time

✔ Toggle Administrator Notifications And Choose Who Send Them To

✔ Modify Notifications Email Templates

✔ Allow Creation Of PTR Record Without DNS Zone

✔ Protect DNS Zones On Product Termination

✔ Manage Client Area Zones Features:

✔ Select Default Template

✔ Toggle DNS Management Link

✔ Choose Scope Of Zones Management:

✔ Allow DNS And rDNS Management

✔ Allow Only DNS Management

✔ Allow Only rDNS Management

✔ Allow Domain/Products/Addon/Other Items Zones With:

✔ Only That Domain

✔ Only That Product Domain

✔ Only Domains From Owned Domains Items

✔ Only Domains From Products Items

✔ Only Domains From Both Owned Domains And Product Items

✔ Any Custom Domain

✔ Exclude Used Domains From Zone Creation

✔ Allow Zones With Related Service IP Addresses Only

✔ Allow Zones With Custom Subnet IP Addresses

✔ Allow rDNS With Custom IP Address

✔ Allow DNS With Custom IP Address

✔ Allow Management Of DNS Record Sets

✔ Display Full DNS Record Names

✔ Allow Management Of Zones Backups

✔ Define Zones Backups Limit

✔ Define Time Interval To Refresh Slave Zones

✔ Choose Whether To Display Zone's Product Name

✔ Display Suggested Nameservers From Submodule

✔ Display DNS Manager Button In Services Sidebar Menus

✔ Define Zone Statuses Displayed In Client Area

✔ SOA Warning

✔ Available Domain

✔ Active

✔ Pending

✔ Define Blocked DNS Strings With Regex Support

✔ Define Logs And Notifications Settings

✔ Define Which Zone Actions To Log:

✔ Create/Terminate Zone

✔ Add/Edit/Remove Record

✔ View Details And Notifications Related To Zones And Servers Load

✔ View Information About Automated Tasks

✔ View Scheduled Tasks Progress

✔ Display Usage Of DNS Servers

✔ View Email Notifications Statistics

✔ View Logs

Client Area Features:

✔ View List Of Owned Packages

✔ View Domain Status

✔ Add And Manage New Zones Within Package Limit

✔ Add And View DNS Slave Zones

✔ View Zones Limit Per Package

✔ Add And Manage Zones Records Within Records Limits

✔ Export DNS Zone To TXT File In BIND Format

✔ View DNS Records Limits Per Zone

✔ Toggle DNSSEC For Zone

✔ View DNSSEC Details Of Zone

✔ Manage In Bulk

✔ Add/Modify/Delete/List DNS Records

✔ Change DNS Record Sets

✔ Delete Zones

✔ Add And Manage rDNS PTR Records Without DNS Zone

✔ Add, Manage And Duplicate DNS Records Sets

✔ Create Zone From DNS Records Set

✔ Manage Zones Backups:

✔ Create Manual Backups

✔ View Automated Backups

✔ Restore Backups

✔ Preview Zones List In Created Backups

✔ Export To File

✔ Import From File

✔ View Bulk Management Tasks

Automation Features:

✔ Provision Packages

✔ Migrate Zones

✔ Import Zones

✔ Clear Unused Zones

✔ Clear Logs

✔ Backup Zones

Server Settings:

✔ Allow rDNS Records

✔ Enable DNSSEC

✔ Allow Multiple PTR Records

✔ Use Cache To Optimize Loading Time

✔ Overwrite SOA Record

✔ Populate Nameservers

✔ Define Nameservers

Package Settings:

✔ Define Zones Limit Per Package

✔ Define Items (Products/Domains/Products Addons) Purchase Of Which Results In Receiving Package

✔ Define If Single Instance Of Package Should Be Assigned To Each Client

✔ Define Servers Used By Package

✔ Define Allowed Record Types

✔ Define Total Records Limit

✔ Define Record Limits Per Type

✔ Define Default TTL For Records

✔ Define Automation Settings For Creating First Zone

✔ Allow To Create DNS Slave Zones

✔ Assign Default DNS Records Set

✔ Allow Client To Create Zone Using Chosen DNS Records Sets

✔ Introduce DNS Management Functionality If Domain Registrar Does Not Support It By Default

✔ Toggle Client And Administrator Notifications

✔ Define Allowed/Blocked IP Addresses For Zones And DNS Records Creation

Supported DNS Servers:

✔ 4PSA

✔ AtomiaDNS

✔ AWS Route 53

✔ BIND 9

✔ CentralNic Reseller (former RRPproxy)

✔ Cloudflare (DNSSEC Support)

✔ cPanel (DNSSEC Support)

✔ cPanel DNSOnly

✔ DigitalOcean

✔ DirectAdmin (DNSSEC Support)

✔ DNS Made Easy

✔ DNS Pod

✔ DNS.com

✔ DynECT

✔ EuroDNS

✔ Freenom

✔ Google Cloud DNS

✔ InterWorx

✔ Nettica

✔ Openprovider

✔ OpenSRS

✔ OVH

✔ Plesk

✔ PowerDNS Hosted

✔ PowerDNS V4 (DNSSEC Support)

✔ Rackspace

✔ Rage4 DNS

✔ Simple DNS Plus

✔ Simple DNS Plus V8 And V9 (DNSSEC Support)

✔ Storm On Demand

✔ Zonomi

Supported DNS Record Types:

✔ A

✔ AAAA

✔ AFSDB

✔ ALIAS

✔ ANAME

✔ CAA

✔ CERT

✔ CNAME

✔ DNAME

✔ DNSKEY

✔ DS

✔ HINFO

✔ HTTPRED

✔ ISDN

✔ LOC

✔ MB

✔ MD

✔ MF

✔ MG

✔ MINFO

✔ MR

✔ MX

✔ NAPTR

✔ NEC

✔ NEC3

✔ NS

✔ NSEC3PARAM

✔ PTR

✔ RP

✔ RRSIG

✔ SMIMEA

✔ SOA

✔ SRV

✔ SSHFP

✔ TLSA

✔ TXT

✔ URI

✔ URL

✔ WKS

✔ X25

General Info:

✔ Supports IDN Zones

✔ AJAX Loaded Pages In Admin Area

✔ Supports Template Customization

✔ Connect With DNS Manager Using Its API

✔ Integrated With IP Manager For WHMCS - Complete Control And Easy Assignment Of IP Subnets

✔ Fully Integrated With Lagom WHMCS Client Theme

✔ Multi-Language Support

✔ Supports PHP 8.1 Back To PHP 7.4

✔ Supports WHMCS Themes "Six", "Twenty-One" And "Croster"

✔ Supports WHMCS V8.9 Back To WHMCS V8.6

✔ Requires ionCube Loader V12 Or Later

✔ Easy Module Upgrade To Open Source Version

[edit] Installation

In this short tutorial we will show you how to successfully install DNS Manager For WHMCS.

We will guide you step by step through the whole installation process.

1. Log in to our client area and download the module.

2. Extract the package and upload its content into the main WHMCS directory.

The content of the package to upload should look like this.

3. When you install DNS Manager For WHMCS for the first time you have to rename the 'license_RENAME.php' file.

This file is located in 'modules/addons/dns_manager/license_RENAME.php.' Rename it from 'license_RENAME.php' to 'license.php'.

4. In order to configure your license key you have to edit the previously renamed 'license.php' file.

Enter your license key between quotation marks as presented on the following screen. You can find your license key in our client area → 'My Products'.

5. In the next step, set up the 'storage' folder as recursively writable.

This folder is available at 'your_whmcs/modules/addons/DNSManager3/storage' .

6. Now you have to activate the module in your WHMCS system.

Go to 'WHMCS Admin Area' → 'System Settings' → 'Addon Modules' . Afterwards, find 'DNS Manager' and 'DNS Manager v3' and activate both addons.

7. In the next step you need to permit access to this module. To do so click on the 'Configure' button, choose 'Full Administrator' and press 'Save Changes'.

Remember to repeat this action for both addons.

8. Good job! You have just successfully installed DNS Manager For WHMCS! Now in your WHMCS system press 'Addons' then press 'DNS Manager'.

[edit] Configuration and Management

If the current version of your module is 3.0 and later, you have access to both DNS Manager and DNS Manager v3 addons.
Please note that most of the module management is already located under the DNS Manager V3 addon, yet some sections are still available under DNS Manager only.
Please navigate to Addons → DNS Manager V3 and follow the below described steps to configure and manage your module successfully, if required, navigate to DNS Manager addon.

This section has been divided into two main parts to allow full and, at the same time, easy understanding of the whole module functionality.
In the first part 'Basic Configuration' an exemplary flow of basic configuration of servers, through creating packages and then zones management
from both the client and the administrator side has been presented.
In the second part, there are described additional settings and tools that can be used while working with DNS Manager For WHMCS.

[edit] Basic Configuration

In the first place we would like to show you the process of configuring your DNS manager on a simple example.
Follow the steps below to see how the process looks like in practice.

Proceed to 'Addons' → 'DNS Manager V3'. There are several sections, but the one that you should be interested in the most in the beginning is named 'Servers'.
You will find it under the 'Settings' tab.

[edit] Servers Configuration

To start your work, add a new server.

To add a new server you must fill out some data to allow connection with it. As an example, we will try to connect with cPanel server.
Additionally, you may declare here whether you need rDNS, Multiple PTR or Cache. Select the desired options.

Please note, that there is also an option Enable DNSSEC available. However, it is currently compatible only with CloudFlare, cPanel, DirectAdmin, PowerDNS V4 and Simple DNS Plus V8 And V9 submodules.
DNSSEC (DNS Security Extensions) - allows enabling validation and authentication of the origin and integrity of DNS data.
If you enable this option, the client will be allowed to turn on DNSSEC for a zone and display its DNSSEC-related details accordingly.

If you want to have the nameserver records populated each time a new zone is created, make sure to check the Populate Nameservers option.

A similar scenario applies to the Overwrite SOA Record checkbox which stands for automatically assigned nameservers in the SOA record.

Once you have chosen a server from the dropdown menu, 'Configuration' and 'Nameservers' tabs appear.
Enter your username, password, Hostname/IP and any other details needed to connect successfully.
Now, press 'Nameservers' and enter the nameservers that will be visible for your customers in their client area.

Remember to save the changes when ready.

Please also note that the configuration differs per selected submodule!

Now, that you have a ready servers on the list, you may manage them. Turn it on/off by changing their status (1.), edit (2.), test connection (3.) and delete (4.).

[edit] BIND 9 Configuration

DNS Manager For WHMCS offers solutions not only for remote DNS servers, but it can also support your own DNS server created using BIND 9.

Please note that currently DNSSEC for BIND 9 is not supported yet.

In this part, we will show you an exemplary BIND 9 configuration.
Firstly, go to the 'Servers' section in the 'Settings' tab, click 'Add Server' and select 'Bind9' module.

Now, move to the 'Configuration' tab and provide essential data to your BIND 9 server configuration.

The 'Path To Bind9 Config Directory' filed is used to locate the BIND 9 'named.conf.local' configuration file.
Please remember that all paths presented on the screens below are only an illustration and you need to adjust to directories paths on your own BIND 9 server.
The module should also have permissions set to access these directories.
Thanks to provided backup paths, you can also easily revert a backup copy in case of any breakdown so it is extremely important to carry out the configuration properly.
Also, note that the module can create a large number of backup files within a newly created 'zones' directory based on the provided path.

Important: Remember that paths to 'Bind9 Config Directory' and 'Backup Directory' should start with / and be absolute.

Another obligatory step to set up is 'Nameservers' . Fill in at least one nameserver and its IP address.

Do not also forget to save the changes.

Once the configuration has been established successfully, you can test your connection, view your ready server which can be easily managed here.

[edit] Management of Packages

Packages - these are collections of settings related to the products for sale.
Thanks to these, the client will be allowed to create specific zones and will possess the access to DNS Management in the Client Area.
Click 'Add Package' to see how to configure it and what exactly can be specified there.

1. In the 'General' section you have to:

name the newly created package
define the number of zones per item (limit of zones that a client may then create within this package)

decide if you allow creating slave zones
Important: The module allows the creation of two types of DNS zones, master and slave ones:
Primary (Master) DNS zones – it is a holder of the original zone file (all the DNS records for the zone). You can manage a host through this zone.
Secondary (Slave) DNS zone – it holds a copy of the zone file. You can use them for better performance, for hiding your primary zones, for backups and redundancy.

2. Here, you can also decide if zones should be created automatically after defined actions.
These are:

New Item - zones will be created automatically for every new product being activated
Pending Domain Transfer - zones will be automatically created for the domains during their transfer:
- Before - a new zone will be created right before launching the transfer to the registrar
- After - the transfer occurs first, and only if it ends successfully a new zone is created
Pending Domain Registration - zones will be created automatically for newly registered domains
- Before - a new zone will be created shortly before sending a registration request to the registrar
- After - a new zone will be created once the status of registration request is received from the registrar
Domain with DNS Management - zones will be created automatically for domains that have been ordered with the 'DNS Management' domain addon
Existing Zone Update - if a zone already exists, it will be updated with newly added record sets

3. Define the maximum, allowed limit of records.

4. Choose DNS Record Sets that will be applied to this package.

Default DNS Record Set - this default set will be automatically applied upon the zone creation
DNS Record Sets - choose the sets created by the administrator that will also be available for clients to choose from when adding a new zone

[edit] Items

Assign Domains, Products or/and Product Addons from available ones to the package. Here you can also allow clients to create their own free zones.

Simply select option under the 'Other' section. Remember that you may use this option for one package only.

[edit] Servers

Assign the package to the previously added server.

Note: You may always assign the package to more than one server.
Due to extra synchronization, you may select which server will be marked as 'Master Server '.
As a result, once you modify the 'Master Server' and run cron commands, all performed changes (such as adding, deleting new records etc.) will be implemented to other servers as well.

[edit] Records

In this part, you may define the record types that you want to enable and declare their limit.

Note: The 'Total' value cannot be lower than the sum of limits set for individual records.

[edit] Notifications

Here, you may configure which notification will be sent to clients and administrators.

[edit] Registrars

In this part, you may allow the 'DNS Management ' option for selected here registrars that do not support DNS management by default.

Please note that the inbuilt WHMCS DNS Management will be used to handle the above functionality.

[edit] IP Management

In the last part, you can specify which IP addresses can be used by your clients while creating a package. If you do not provide anything, clients can use any IP addresses without any limitations.
The 'IP Addresses Blacklist' section allows you to ban IP addresses. This will prevent users from using specified IP addresses.

Remember to save the changes when the package configuration is ready.

Enable the newly created package to allow it to be used!

[edit] Client Area

In order to take advantage of the brand new management page in the client area, you need to allow access in the DNS Manager v3 addon.
Navigate to Addons → DNS Manager v3 → Settings → Global Settings, and enable 'DNS Management Link.' This will enable a 'Manage DNS' button in the Client Area.

Next navigate to Addons → DNS Manager v3 → Settings → General. There you will find two sections: 'Cron task' and 'Module Settings'.

Cron Task - set up this cron task in order to successfully run tasks added in the 'Bulk Management' section in the client area. We recommend setting up a 5 minutes interval:

php -q /home/your_whmcs/modules/addons/DNSManager3/cron/cron.php queue

Module Settings - enable to overwrite the DNS Manager v2 link of the client area

Note: If you do not enable this option, your clients will still have access to the previous view of the 'Manage DNS' page, still available for DNS Manager v2.x.x users.

[edit] DNS Management in Client Area

Now, that we already have the module configured you may see how clients will add and then manage their zones.
In the client area find the button 'Manage DNS', it will redirect you to the management page.

[edit] Zones

In here, clients may add new zones. To do so, simply type in the name of the zone and choose IP address from the available or enter your custom IP.
It depends on your configuration - read more about possible options here.
From the dropdown menu clients can also define record sets. If they do not have any added, the default one created by the administrator in the admin area will be selected.
When clients create sets by themselves, they can use the one defined by them as default, or choose other one from the list.

Standard list view of DNS Zones:

Note: You can turn on this mode in the 'DNS Manager v3 addon' → 'Settings' → 'Global Settings' → 'Other' → 'Zones Single Table View'.

The module gives you the possibility of creating two types of zones. These are master zones and slave zones. For more info please read this section.

Form to create a master DNS zone:

If you wish to create a slave zone, this is how the form will look like:

Allowed actions on a zone:

edit an existing zone
delete zone

Press 'Edit' to see details of the zone, you may edit the zone here and add new records if limits allow you.

Enter a new record's name, choose the type from available etc.

In the case of slave zones, press the dedicated icon (2.) to only view the zone records list.

You may force the slave zone to refresh by pressing the button (1.) - related to slave zones on servers other than PowerDNSv4.
A new task will be added to the queue and the zone will be refreshed with the setup time interval.

[edit] DNSSEC

If the 'Enable DNSSEC' option has been selected ('CloudFlare', 'cPanel', 'DirectAdmin', 'PowerDNS', 'PowerDNS V4' and 'Simple DNS Plus V8 And V9' submodules), the client may turn it on.

To do so, navigate to 'Additional Actions' → 'DNSSEC'.

Enable DNSSEC here, you will then get access to DNNSSEC details for the zone, including keys and delegation signer records.

Press 'Rectify Zone' to comply with DNSSEC.

[edit] Bulk Management

Under this section you may manage numerous DNS zones. Select at least one zone on the list and press the 'Choose Action' button.
There are six allowed actions that can be preformed on zones.

Allowed actions:

Add Record
Modify Record
Delete Record
List Records
Change Record Set
Delete Zones

Add Record - define the newly created record type, name, TTL and address.

List Records - search for records manually by typing in exactly what you need or enable 'Regular Expression' to broaden your search results.
Use regex syntax, for example:

/abc/ - all records including "abc" string (lower case only)
/[\d]+/ - all records including numbers
/^www/ - all records that start with "www" (lower case only)
/\.com$/ - all records that end with ".com" (lower case only)
/[abc]/i - all records that include "a," "b" or "c" letters (lower or capital case, any position)

Modify Record - you may modify existing records. Search for records manually by typing in exactly what you need or enable 'Regular Expression' to broaden your search results.
Use regex syntax, for example:

Search: /(\d+)abc/i
Replace With: def$1

The above example will result in exchanging all records that include a string of numbers followed by abc letters to a 'def' phrase with the same string of numbers:

phrase2137abc → phrasedef2137

Delete Record - select the record type and specify which records shall be deleted. Enter specific data or use regular expression.

Change Record Set - choose a new record set. You may enable the 'Wipe Records' option to clear the selected zone at the same time.

Delete Zones - remove all the selected DNS zones.

[edit] rDNS

If you have allowed the rDNS management in the client area by selecting either 'Allow DNS And rDNS Management' or 'Allow Only rDNS Management' option (read more here) in global settings,
your clients can create PTR records for IPv4 and IPv6 addresses without any related zone. To do so, press 'Add PTR Record'.

Select related item, then depending on the configuration enter IP address or choose IP or Subnet from the available list.

Note: Subnets are available only if you have integrated your DNS Manager with IP Manager For WHMCS - see below options for more details.

Your newly created rDNS record should appear on the list. You may edit RDATA or delete the record completely.

[edit] Record Sets

You can add and manage records sets in the 'DNS Record Sets' section as shown below.

Click the 'Add Record Set' button and provide the necessary details.
It can be also set as default.

Your newly created DNS record should appear on the list. You may edit the record set, edit general record set data, duplicate or delete it completely.

[edit] Backups

Backup Tasks

You can manage fully your zones backups. Move to the mentioned section to see any options.
Note that this option must have been previously allowed by your administrator in general settings. Press the 'Create Backup' button to start.

A new task is added immediately. Now, all you need to do is edit the added backup task and there select the zones from available that will be processed and stored in a backup file.

Press the 'Create Zones Backup' button when ready.

The just added task to back up the zones is now visible on the list of all tasks. There are also information on the task progress and number of zones already processed.

To see details, press 'Show List' button.
Important: Keep in mind that you must wait until the next execution of the "Cron Importer" to start processing. If it is set to more than 5 minutes, you will not see the results on the run.

Manual Backups List

Here you will find a list of all files with a number of backed up zones. In order to upload a ready backup file, simply press the 'Upload File' button.

Select the file from your store, keep in mind that only the previously downloaded backup files can be used.
Surely, such file can be edited in any editor to adjust the records inside it to your needs, but you must be careful and stick to its form.

Use the action buttons to start the tasks:

1. - Show Backup File Content
2. - Download the file.
3. - Restore backup file. This action, when stared, is also visible on the list of tasks above.
4. - Delete the file.

[edit] Tasks

You will find a list of current tasks in 'Tasks' section.
Among all tasks there are import tasks, migration and synchronization tasks.

According to specifically set-up cron jobs all created tasks are regularly executed. Here, you can see the current status of each task.
If it is queuing for the next cron run, is currently executed, aborted or complete. Check when they were executed for the last time (Last Execution) and when the task was added.
Available actions: call execution manually and remove the task.

[edit] Zones Management

In the administrator panel, you can spot all your client zones. You are free to preview those already existing.
You will see whose zone it is, its type, on which server it is created and its status (created/deleted).

You can always add a new custom zone directly for your client from your admin area.

To do so, press the button marked on the screen below.

Now, you are required to fill out the visible fields.

If you select a service that is in a package with the allowed option to create slave zones, a dedicated switcher will appear.

Important: The module may create two types of zones, master and slave ones. Master type zones are created on DNS servers and the records are synchronized via AXFR protocol by itself.
In the case of slave zones, the module creates a slave zone on DNS servers and that is the DNS server that performs the synchronization.
("PowerDNSV4" only, in the case of other servers like "cPanel", you have to manually force the synchronization).

Note that both the admin and client area allow the user to apply a record set to a single or to multiple zones.

Actions on zones from the admin area:

Change Related Item - choose one of the available items from a dropdown menu and save changes
Edit DNS Zone Records- modify existing records or add new ones
Add DNS Zone - use this button to create a zone on the server
Import DNS Zone From File - choose a file from which zones will be imported
Export DNS Zone To File - choose a file to which zones will be exported
Export DNS Zone To TXT File In BIND Format - a TXT file will be saved just after pressing the button
Lock/Unlock DNS Zone - if you lock a zone, it will not be possible to edit this zone in the client area
Delete DNS Zone - if you use this button, the zone will be deleted both from WHMCS and from the server
Remove DNS Zone From WHMCS - zone will still be available on the server
Refresh Slave Zone - press this button to manually add the task to the queue and force refreshing a slave zone via AXFR protocol (slave zones created on servers other than PowerDNSv4)
View DNS Zone - press to see a list of records; you may also refresh the slave zone from this level (slave zones only)

[edit] Additional Tools

[edit] Settings

Remember that if you want to redirect your clients to DNS Management page in V3.0, you must previously configure the dedicated addon settings.
Move to Addons → DNS Manager v3 → Settings → General. There you will find cron task that you will need to execute in order to allow bulk actions on zones in the client area to be performed.

Furthermore, in order to redirect your client to a brand new client area page of the DNS Manager v3.0, please enable the option to overwrite the client area link.

[edit] Global Settings

This section has been designed to allow quick and simple configuration of global settings from one place.

[edit] Templates

Choose a default template that will be used in the client area.

If you have more than one template then you may allow your clients switch between them.
Decide whether you wish to use a ready-configured redirection to the DNS Management page in the client area.

[edit] Logs And Notifications

In this part, you may impose when log entries and notifications should be removed from the system database.
If you wish you may also check the 'Log Successful Actions' option to store all entries in logs (DNS Manager → Settings → Logs).
'Log Zone Actions' - select single actions on zones, logs on them will be stored in the module as well.

[edit] Slave Zones

The following section is dedicated to the created in the module slave zones on servers other than PowerDNSv4 (in its case, the slave zones are refreshed automatically).

Here, you may define the time interval at which the slave zones will be refreshed and their information synchronized with a remote DNS master server using the AXFR protocol.
Note that the time is measured in hours.

[edit] Other

The box with 'Other' options available is a crucial part of configuration where you can manage IP Manager For WHMCS module and manage PTR records creation.
Besides, here you can switch off the guide with simple instructions visible on the dashboard.

1. Client Area Management - depending on the configuration, the client has access to:

DNS And rDNS Management - give your clients full access to DNS management in the client area.
rDNS Management Only - create PTR records for IPv4 and IPv6 addresses without a related zone.
If this option is enabled your clients will be only allowed to add reverse DNS with no zone related. Other sections are blocked
DNS Management Only - the 'rDNS' tab will be blocked for the client

2. Domain/Product/Addon/Other Item Options - restrict clients to manually create zones using the indicated domains only.

Allow Only That Domain
Allow Only That Product Domain
Allow Only Domains From Domains Items
Allow Only Domains From Product Items
Allow Only Domains From Domains And Product Items
Allow Custom Domain

3. Exclude Used Zones From Zone Creation - select to exclude the already used domains from the possibility of being used again in a newly added zone

4. Related Service IP Addresses Only - create zones and PTR records with a related IP address only.
When adding a new zone/PTR record you can choose from available hosting related IP addresses only as marked on the screen below.

5. Custom Subnet IP Address - create zones and PTR records with an IP address included in a subnet related to the product.

Note: This option works only if you have integrated your DNS Manager with IP Manager For WHMCS.

5. rDNS Custom IP Address - create PTR records with a custom IP, enter a new IP address to create a new PTR.
Note: Both IPv4 and IPv6 are supported by DNS Manager For WHMCS.

6. Custom IP Address - create zones with a custom IP address. If you have no IP addresses to choose from, you have to enter a new IP address.
Note: Both IPv4 and IPv6 are supported by DNS Manager For WHMCS.

7. Client Area Record Sets - clients may manage DNS records sets.

8. Client Area Backups and Client Area Backups Limit - clients are given the option to create backups of their zones and upload backup files.
It is advised to set a limit on the number of allowed backups. Default '-1' indicates unlimited

9. Protect Zones On Product Termination - zones are not automatically deleted once the product has been terminated.

10. Show Product Name - a full product name is shown, instead of the general type with an order number.

11. Show Nameservers - submodule nameservers will be displayed in the 'Edit Zone' section of the client area.

12. Show DNS Manager Button - the 'DNS Manager' button will show up in the sidebar section of products which have zones created.
Thanks to this button you can easily move to the 'Edit Zone' section.

[edit] Notifications

In this part, set which notification should be sent to clients and which to the administrator. Select the ones that interest you.

Press 'Modify' and you will be quickly redirected to the email template page where you can adjust it to your needs.

Use the 'Exclude' button to specify domains, products and addons that the zones assigned to them will NOT be included in notifications.

Use the 'Include' button to specify which admin users will receive notifications.

[edit] Client Area Zones Status

Checking the selected boxes will result in an additional status concerning a given domain in the client area.

Pressing the Modify button next to a given option will cause a new window to appear where you can set up your own custom status by means of HTML.

Your new description can include the {$domain} variable which will give the domain address back in the status message.

You can see an example status on the screen below.

[edit] DNS Record Sets

Create ready made sets of DNS records. You will find them in 'Settings' → 'DNS Records Sets'.
Press 'Add Set' to create a new one.

Enter the newly created set name.

Once your new set appears on the list, you may edit that set in order to create records. Press 'Edit Record Set' to continue.

List of records will appear. Please use the 'Add Record' button to continue.

Now, fill out the data as required.

Note: You may add adequate variables for domain and IP address and then these fields will be automatically changed to domain/zone IP when this record set is used.
For example, if you have the 'example.com' domain with '123.123.123.123' IP address all you have to do is add the following variable to the DNS Record Set:

{$domain} - will return full 'example.com' domain address
{$domainname} - will return only 'example' name
{$domainextension} - will return 'com' extension
{$ip} will return the '123.123.123.123' IP address; that can be:
- IP address assigned to the domain by a client, provided while creating a zone
- hosting dedicated IP address
- WHMCS server address provided it is a hosting
{$serverhostname} - will return the DNS server address or its IP address, depending which one has been provided in the module's DNS server configuration in the admin area,
e.g.: yourdnsserver.com or 12.23.34.45
{$ns1}, {$ns2}, {$ns3}, {$ns4} and {$ns5} - will return the global nameservers addresses specified in the order basing on the sequential number of the corresponding data in the variables
{$serverassignedipX} – allows you to use 'Assigned IP Addresses' from another server configuration ( WHMCS → System Settings → Servers).
Important! You need to replace X with a number. For example: If you provide {$serverassignedip1} in the DNS Record Set, the first address from the 'Assigned IP Addresses' section will be used.

Created DNS Records Sets can be then used while preparing ready packages, as it was described.
Ready made sets allow much faster and more personal configuration of packages.
There is also the possibility to duplicate the selected DNS Record Sets.

[edit] DNS Blocked Strings

Proceed to Settings → Blocked Strings now.

In this section you may define a lists of words that will not be allowed to be used while creating DNS and rDNS records.

In order to add certain words, simply type them in the adequate box.

Allowed formats:

each word in new line

space separated

coma separated

coma with space separated

Allowed regular expression options:

test* - all expressions that begin with a 'test' word

*test - all expressions that end with a 'test' word

rec...ord - three dots inside will block all expressions with any three signs inside a word

rec*ord - an asterisk inside will block all expressions that begin with a 'rec' and end with a 'ord' as in example

You may create a separate list for DNS records and another one for rDNS or create one shared list for both of them.
In the latter case just select the 'Use same values as for DNS' option like on the screen below.

At the very bottom, you may also create a list of clients who will be excluded from the above restrictions.

All the other clients will have to follow the 'Blocked Strings' rule. Remember to save the changes in the end.

In practice, when a client will be trying to create a record using one of the forbidden words, the action will be blocked.

[edit] DNS Manager Logs

This section helps you keep track of all the activities carried out in DNS Manager. Find them here: 'Settings' → 'Logs'.

[edit] DNS Manager Tasks

Check the list of current tasks. Keep in mind that tasks management is still in the DNS Manager V2 addon!

Use the cron tasks to delete all tasks with the 'Finished' status:

php -q /yourwhmcs/modules/addons/DNSManager3/cron/cron.php TasksCleaner --clean

[edit] DNS Manager V2 Addon

To manage the following setting you will have to step back to the DNS Manager v2 addon module for a moment. You will find there the remaining section described below.

[edit] Cron Jobs

In order to manage your cron job tasks proceed to 'Tools' → 'Cron'.
Here, you will find five information boxes, each one responsible for management of a separate cron task.
These are: migration, import, synchronization, cleaner and backup.

At the very top, there is an info box with general cron details, such as recommended time interval of a cron execution (5 minutes is suggested),
the last execution time and run time period. (Keep it as frequent as possible!)

Cron Migration - responsible for calling added tasks to migrate zones between servers.
Choose an interval and declare how many zones can be migrated during a single execution.

Cron Importer - responsible for calling added task to import zones from an external server to WHMCS.
Choose an interval and declare how many zones can be imported during a single execution (Admin and Client backup tasks).
Select option to automatically check recognized records to perform the import much faster.
Mark Active Users/Services and only such will be imported.
Import Priority - decide whether these should be services that will be assigned to a client firstly ('Services, Domains' sequence) at Related Itmes or domains if selected the other way round.

Cron Synchronization - this cron job is responsible for regular synchronization of created zones.
Choose interval and declare how many zones can be synchronized during a single execution.
Note: When NS records are inconsistent with nameservers set in the server configuration, this cron job also deletes the zones.

Cron Cleaner - this option is a little bit more complex. Just like in case of other cron jobs, firstly choose an interval and declare how many zones should be cleared
during a single execution. Then you may specify conditions of clearing zones and records.

Warning! By default, the cron job is disabled and the 'Notify Only' option is enabled.
You will need to change these settings manually if you would like to have the zones removed.
What is more, when the cron will be enabled and the 'Notify Only' feature disabled, the module will send the warning about the zones deletion as an additional layer of safety.

Zones are removed:

Not Included In Package - if no longer match with any package
Not Modified For - have not been modified for a specified period of time
Not Found In WHOIS - their domain is not found in WHOIS Lookup
Without Records - no chosen records are included
Inactive Services - with canceled, terminated and/or suspended status
Inactive Domains - with canceled and/or expired status

Decide for which of the following services, the PTR Records should be removed:

Terminated Services
Cancelled Services
Suspended Services

Cron Backup Scheduler

In this section, you can schedule your backups. Similarly as previously, complete these fields according to your preferences.

Automatic Backup Limit - you can set a maximum number of backups that will be stored. If the provided number is exceeded, then the oldest backups will be overwritten.

[edit] Import

Import - this is an additional tool that allows to import zones that exist on outside servers to WHMCS.
Move to Tools' → 'Import' in your admin panel. You will find here a list of 'Import' assignments with information on which server they are imported from,
total number of already imported zones and the number of all zones, progress of import task.

To add a new import task press 'Add Import'.

Choose a server that you want to import zones from.

Now, when the new import task appeared on the list of awaiting imports, schedule the action.

When schedule is confirmed, preview the list of imported zones to assign a client and a related product to the zone.

To do so, press the button as marked on the screen.

A list of zones appears.

DNS Manager Import tool detects the client and product which the domain and IP address is assigned to and automatically designates related client and product to migrate.
You can also do it manually by selecting a client and product from the list of available.
When ready, press 'Import Zones' to import several zones at once or use action buttons for a single import.

If you do not schedule import tasks, regular cron execution will trigger the import.
However, you always have to make sure that selected zones are assigned to related clients and products.

[edit] Zone Backups

The 'Zone Backups' section allows you to export your zones to the file and, when needed, easily import them on the server.

To export zone automatically, press 'Export To File', define from which server you wish to export it and click on 'Add.'

Schedule the task. Remember to confirm the action.

You can now move to the list of zones to assign clients and products. Press the button marked on the screen.

Select zones using action buttons next to single zones and 'Import Zones' for mass import.

You can also manually export zones. All you have to do is press the 'Add Export' button, then choose the appropriate server and source file.

[edit] Tasks

You will find a list of current tasks in 'Tools' → 'Tasks' section.
Among all tasks there are import tasks, migration and synchronization tasks.

According to specifically set-up cron jobs all created tasks are regularly executed. Here, you can see the current status of each task.
If it is queuing for the next cron run, is currently executed, aborted or complete. Check when they were executed for the last time (Last Execution) and when the task was added.
Available actions: call execution manually and remove the task.

[edit] Dashboard

The home page of DNS Manager which can be used to get a quick and clear preview on the crucial parts of the module: added servers with number of zones created on them,
summary of email messages sent to clients and finally the most important notifications.

[edit] Custom cPanel Zone Templates

You can allow your customers to create zones without cPanel Default Records. To do so, you need to create your own Zone Template in the WHM.

If you do not know how to create your own Zone Template, you can follow this short guide made by cPanel: Edit Zone Templates Guide
To apply your newly created zone template simply log in to your WHMCS and go to 'Addons' → 'cPanel Extended Functions' → 'Configuration'.
As a module choose 'cPanel' and enter the name of your zone template in the 'Template' field as shown on the screen below. Remember to save changes.

[edit] IP Manager For WHMCS Integration

As it has been mentioned above, some of the options in our DNS Manager For WHMCS are available if you are also using IP Manager For WHMCS simultaneously.
In this section you will learn how to integrate the two products to work together. For more inforamtion on the IP manager module configuration please refer to our documentation.

Let us take a look at the IP Manager module firstly. There you have to create a subnet.

You can do it ether for IPv4 or IPv6 type. DNS Manager For WHMCS supports both types.

When ready, create a proper configuration and assign required products to it.

Assign created subnet to this configuration.

Under 'Relations Configuration' → 'Products' define the number of IP addresses that will be allowed for a client.
By default this is only one address.

Move to DNS Manager now and create an appropriate package where you declare limits for zones, select the product and allow records types and limits
that will be provided within the purchased service.

Now, a client upon purchase of such service may now use assigned IP addresses from the subnet and manage the DNS zones and rDNS zones according to limits specified in the package.

The client may now add PTR records within the related service.

Create zones with IP addresses included in a subnet related to a service in IP Manager.

You only need to remember that relevant options must be enabled in the 'Global Settings' section.

[edit] DNS Manager Migrator

If you have been already using DNS Manager For WHMCS, you can migrate data from your current system to the latest version.
To do so, follow the below steps:

1. Activate DNS Manager For WHMCS V2.x.x.
2. Run the following command in your browser or in the console:

your_whmcs_path\modules\addons\DNSManager2\cron\migration.php

3. Follow the steps that you see on your screen now!

Note: It is advised to use your console to do the migration between the previous and the new versions of your DNS Manager in case you have a huge number of zones
(if more than 1000, it is highly recommended).
4. Once the script has run and the migration is complete you need to review the configuration of your servers to alter their naming and which is the most important enable migrated servers and packages.
Freshly migrated servers and packages are by default disabled.

Once the migration of zones is ready you can migrate rDNS records.

To do so:
1. Run command in your browser or in console:

your_whmcs_path\modules\addons\DNSManager2\cron\ptr_migration.php

2. Follow the steps that you see on your screen now.
3. Your PTR records will be assigned to adequate zones. In case when the pointing domain does not exist, the required zone will be created and added to the client's account (if no other user already has it).
4. Migrated rDNS records are visible in edition page of its zone as PTR records.

[edit] API Methods

You may access your DNS Manager For WHMCS API. Here is a short instruction how to do that:

The main required command that has to be used is:

'dnsmanager'

Additionally, you have to define 'dnsaction' with some specific value.
Note: the 'action' parameter is no longer used since the 2.7.0 version due to not being allowed as a method to be executed as external.
These specific values can be:

'getServerList' - returns the list of servers in DNS Manager
'saveRDNS' - allows adding new rDNS record. Additional parameters are required here, these are:
- 'serverid' - ID of a server
- 'ip' - IP address that will be used
- 'clientid' - ID of a client, record will be assigned to that client
- 'ttl' - value of TTL for record
- 'rdata' - record's value
'removeRDNS' - allows removing existing rDNS record. Additional, required parameters:
- 'serverid' - ID of a server
- 'ip' - IP address that will be used

Exemplary use:

<?php
  // Set Vars
  $command = 'dnsmanager';
  $values = array( 'dnsaction' => 'getServerList', 'params' => array() );
  $adminuser = 'DemoAdmin';

  // Call API
  $results = localAPI($command, $values, $adminuser);
  var_dump($results);
?>

Since the 2.7.0 version, there are new methods available:

'createZone' - creates a zone. Additional parameters are required here, these are:
- 'action = dnsmanager'
- 'dnsaction = createZone ' - DNS action, that DNS Manager should execute
- 'zone_name' - name of the zone being created
- 'type = 1 or 2' - type of related item. Use 1 for domain or 2 for the product
- 'relid' - ID of the related item (hosting ID, domain ID)
- 'userid - ID of user
- 'zone_ip' - IP address assigned to the zone. If empty, a default IP address will be used
- 'recordSet' - ID of the DNS Record Set, it can be downloaded from the base, table: ' dns_manager2_setrecord', field: 'setid'

Exemplary use:

$postfields = array(
 'action' => 'dnsmanager',
 'dnsaction' => 'createZone',
 'zone_name' => 'zonename.com', 
 'type' => '1',
 'relid' => '2',
 'zone_ip' => '192.168.56.101',
 'userid' => '1',
 'recordSet' => '2',
);

'updateZone' - updates records of the zone. Use with these parameters:
- 'action = dnsmanager'
- 'dnsaction = updateZone' - DNS action that DNS Manager should execute
- 'zone_id - ID of the zone that should be updated (use ID from WHMCS)
- 'records - array of the records that should be updated (added/changed/removed) if DNS Manager compare these records and add/change/remove corresponding difference. These are:
  - 'name' - name of the node to which this record pertains
  - 'type' - type of the updating resource record (e.g. MX)
  - 'class' - class node
  - 'ttl' - number of seconds that the RR stays valid (e.g. 14400)
  - 'data' - additional specific RR data

Exemplary use:

$result = localAPI('dnsmanager' ,
    array(
      'dnsaction' => 'updateZone',
      'zone_id' => 2,
      'records' => array(
        array(
          'name' => 'example.website.com',
          'type' => 'A',
          'class' => 'IN',
          'ttl' => '14440',
          'data' => '192.168.56.101',
        ),
        array(
          'name' => 'example.website.com',
          'type' => 'A',
          'class' => 'IN',
          'ttl' => '14440',
          'data' => '192.168.56.102',
        ),
      )
      ),'admin');

'getZone' - returns the zone with records. Use with these parameters:
- - 'action = dnsmanager'
  - 'dnsaction = getZone' - DNS action that DNS Manager should execute
  - 'zone_id' - ID of the zone that should be retrieved (use ID from the dns_manager2_zone table)
  - 'zone_name' - name of the zone

'removeZone' - deletes the zone. Use with these parameters:
- - action = dnsmanager'
  - dnsaction = removeZone' - DNS action that DNS Manager should execute
  - zone_id' - ID of the zone that should be removed (use ID from WHMCS)

[edit] Tips

1. Keep track of your 'pending' and in 'progress' 'Tasks' to set an optimum interval time for the tasks execution.

For example, set an interval in the way that half of the time task is set to the pending status.

2. While using the OVH submodule, note that each time a client wants to remove a zone, the administrator will receive an email sent by OVH. Only after its confirmation, a given zone will be terminated successfully.

3. 255 characters in TXT records is a maximum limit for the 'PowerDNS' and 'cPanel' submodules.

4. As this module supports templates system, any changes made in the module's templates files will be saved after the upgrade process.

5. In case you are using cPanel or cPanel Extended provisioning modules with DNS Manager, it is highly advised to enable the Existing Zone Update option.
Otherwise, DNS zone will be previously created by the provisioning module, not by DNS Manager where an error notification on already existing zone will appear. That will cause such zone will not be visible on the Zones List.
If the mentioned option is enabled, DNS Manager will fail to check whether the zone already exists and consequently the created by the provisioning module entry will be added to the Zones List.

6. Please note that from the 2.13.0 version of the module, it is obligatory to use a dot at the end of each domain while adding or editing 'DNS Records' and 'DNS Record Sets' .
If you do not provide a dot, the module will double your domain. Take a look at the following examples, on the left side we present what is typed by a client and on the right side you can see the module’s interpretation:

An exemplary zone name is example.com
@ → example.com.
example.com → example.com.example.com.
example.com. → example.com.
www.example.com. → www.example.com.
www.example.com → www.example.com.example.com.
www → www.example.com.
www. → www.example.com.
www.@ → www.example.com.

7. Now you may use 'API Token' instead of 'API Key' to configure the Cloudflare submodule. Before you generate your 'API Token' in your Cloudflare panel, please remember to set the following read/edit permissions there:

User/User Details – Read
Zone/Zone – Edit
Zone/Zone Settings - Edit
Zone/DNS - Edit

8. How to correctly add translations of the DNS server errors into the language file:

Most errors include a string with a domain name, to add a custom error message, you have to replace this string with :domain_word: phrase.
An example of currently displayed error message:

 RRset A.testdnsipdefault.by. IN CNAME: Conflicts with pre-existing non-CNAME RRset

In this case A.testdnsipdefault.by. must be replaced with :domain_word:
A correctly generated lang snippet will look as follows:

 $_LANG['addonCA']['dashboard']['errors']['RRset :domain_word: IN CNAME: Conflicts with pre-existing non-CNAME RRset'] = "Some serious problem occurred with :domain_word:";

As a result the below message will be displayed in the module:

 Some serious problem occurred with A.testdnsipdefault.by.

Of course, you may skip the domain name in the final output or add a fully customized error message:

 $_LANG['addonCA']['dashboard']['errors']['RRset :domain_word: IN CNAME: Conflicts with pre-existing non-CNAME RRset'] = "Some serious problem occurred";
 $_LANG['addonCA']['dashboard']['errors']['RRset :domain_word: IN CNAME: Conflicts with pre-existing non-CNAME RRset'] = 'My custom translation';

If you do not add any translation in to the lang file, an original error message will be displayed.

[edit] Update Instructions

The essential guidance through the process of updating the module is offered here.

Ensure successful completion of the module update by carefully following each step, thereby preventing data loss or any unforeseen issues.
Additionally, you will find a current list of supplementary actions necessary for a smooth update process there.

[edit] Migration from V2x.x to V3.x.x

If you want to migrate your DNS Manager For WHMCS to version 3.0, please follow the below steps:

Keep both module addons DNS Manager and DNS Manager v3 active
Full module configuration is still located in DNS Manager addon module, your old data are not lost
Move to DNS Manager v3 addon module → 'Settings' to enable access to Client Area with support for 'Twenty-One' theme
- Set up a new cron task (DNS Manager v3 addon module → Settings)
Go back to DNS Manager addon module → 'Settings' → 'Global Settings' → 'Client Area Zones Status' and again save the content.
Note: Entered content might not be correctly displayed in the new client area view, saving the changes will ensure there are no unexpected errors or missing information.

[edit] Migration of Zones

'Migration' is another useful tool that you may use to manage zones efficiently. With this tool you may migrate zones between servers.

Keep in mind, that if you wish to transfer the relation that exists in the DNS Manager module to the target server, you must select the 'Move Management To Target Server' option.
Otherwise, only the zone will be copied from the original to the target server, the relation to the original server will remain in the module.

Remember that migrated zones are available on both servers now! Migration does not delete zones, just copy them to the new server!

To add a migration task, press 'Add Migration', specify from which server you wish to migrate zones, and the target server, as simple as that.

Note 1: Migration does not copy DNS Manager settings, to illustrate: if you are migrating zones that exist in DNS Manager their locations for example are not updated.
Note 2: You can decide if the option of managing zones should be transferred to the target server. To do it, please tick 'Move Management To Target Server' .

Schedule the migration. Remember to confirm the action.

Move to the list of zones to assign clients and products. Press the button marked on the screen.

Select zones and 'Migrate Zones' for mass migration or use action buttons next to single zones.

[edit] Upgrade Guide

Seeking a solution that offers greater flexibility, customization tailored to your precise needs, and unrestricted availability?
There is an option that not only proves to be cost-effective in the long run but also includes prioritized support services, making it a truly valuable investment.

Opt for the Open Source version of your DNS Manager For WHMCS module to unlock these benefits.
Simply click on either the Get Source Code or Upgrade To Lifetime button found on the product's page in our client area to complete the one-step upgrade process, with a dedicated discount already applied.

Follow a comprehensive guide covering the transition process, the advantages it brings, and step-by-step instructions on what to do next after the order has been successfully finalized.

[edit] Common Problems

1. When you have problems with connection, check whether your SELinux or firewall does not block ports.

2. jQuery 1.9 is required to work properly.

3. In case you cannot see any zone records in your client area after import or migration actions, then disable cache for the DNS server.

To do so, edit the 'General' section of the server.

4. Once you have problems with manually created zones for specific domains, along with the 'Subdomain is not allowed' or 'Invalid zone name' error,
make sure to add the .tld that you would like to use to the following file:

modules\addons\DNSManager2\storage\tld.list

5. In case your backup task started in your client area is not being processed, make sure that your Cron Import job is not disabled or set to a low frequency.

6. Error: "The selected zone is already taken"

Reason 1: A zone with the same name already exists in dns_manager2_zone table (you can also find it on the 'Zones List' in the addon)
Reason 2: Other client is using such domain with a product or has it registered. It is allowed as long as the other client's domain status is: Cancelled, Transferred Away, Fraud or Terminated
Solution: Find the domain in WHMCS and cancel it
Reason 3: Zone already exists on the DNS server (e.g. cPanel)

7. Error: "Message: API failure: (XID 2ugbb6) You do not have access to a domain named “domain.tld”."

If you encounter the above error for a zone associated with a cPanel server, it means that you need to set root user permissions for the token that is used in the cPanel submodule configuration.

Seeking a solution that offers greater flexibility, customization tailored to your precise needs, and unrestricted availability?
There is an option that not only offers cost-effective, long-term maintenance but also includes prioritized support services, making it a truly valuable investment.
Opt for the Open Source version of your DNS Manager For WHMCS module and unlock these benefits.
Simply use either the Get Source Code or Upgrade To Lifetime button found on the product's page in our client area, and proceed with our one-step upgrade order with a dedicated discount already applied.
Follow a comprehensive guide covering the transition process, the advantages it brings, and step-by-step instructions on what to do next after the order has been successfully completed.

@@ Line 2: / Line 2: @@
 <meta name="description" content="ModulesGarden Wiki Contains All The Information You Need About The DNS Manager For WHMCS Module."></meta>
-=About [https://www.modulesgarden.com/products/whmcs/dns-manager DNS Manager For WHMCS]=
+<h5 style="color: #ff0000; font-weight:bold; text-align:center;">DNS Manager V3 For WHMCS requires an active DNS Manager For WHMCS.<br/>
+You must keep both addons active to be able to use the newest version of DNS Manager module in full.</h5>
+=About [https://www.modulesgarden.com/products/whmcs/dns-manager DNS Manager V3 For WHMCS]=
 {|
-|style="padding: 10px 0px 10px 0px;"|'''DNS Manager For WHMCS''' is an end-to-end module that enables your customers to be in charge of their DNS zones.<br />
+|style="padding: 10px 0px 10px 0px;"|'''DNS Manager V3 For WHMCS''' is an end-to-end module that enables your customers to be in charge of their DNS zones.<br />
 Thanks to a wide variety of submodules, combined with options allowing you to prepare ready packages, your DNS Manager For WHMCS is there for you to surely meet your expectations.<br />
 As an administrator you have full control over DNS zones and possess access to a broad range of management options.<br />
 <br />
-Wiki of DNS Manager For WHMCS 1.9.10 can be found [http://www.docs.modulesgarden.com/index.php?title=DNS_Manager_For_WHMCS&oldid=19472 here].
+Wiki of '''DNS Manager For WHMCS 2.x''' can be found [https://www.docs.modulesgarden.com/DNS_Manager_2.X_For_WHMCS here].<br/>
+<!--Wiki of '''DNS Manager For WHMCS 1.9.10''' can be found [http://www.docs.modulesgarden.com/index.php?title=DNS_Manager_For_WHMCS&oldid=19472 here].-->
 |}
 <!--a comment maybe? -->
@@ Line 23: / Line 27: @@
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ View And Edit Existing Zones
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Add And View DNS Slave Zones
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Lock/Unlock Zones From Edition By Clients
 |}
 {|
@@ Line 29: / Line 39: @@
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ Import Zones From Chosen Server
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Export Zone To TXT File In BIND Format
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Auto-Synchronize Zones And DNS Records Between Multiple Servers
 |}
 {|
@@ Line 34: / Line 50: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Define DNS Records Set
+|style="padding: 0px 0px 0px 30px;"|✔ Define, Manage And Duplicate DNS Records Set
 |}
 {|
@@ Line 116: / Line 132: @@
 {|
 |style="padding: 0px 0px 0px 45px;"|✔ Allow Management Of DNS Record Sets
+|}
+{|
+|style="padding: 0px 0px 0px 45px;"|✔ Display Full DNS Record Names
 |}
 {|
@@ Line 122: / Line 141: @@
 {|
 |style="padding: 0px 0px 0px 45px;"|✔ Define Zones Backups Limit
+|}
+{|
+|style="padding: 0px 0px 0px 45px;"|✔ Define Time Interval To Refresh Slave Zones
 |}
 {|
@@ Line 130: / Line 152: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Define Zone Statutes Displayed In Client Area
+|style="padding: 0px 0px 0px 30px;"|✔ Display DNS Manager Button In Services Sidebar Menus
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Define Zone Statuses Displayed In Client Area
 |}
 {|
@@ Line 186: / Line 211: @@
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ Add And Manage New Zones Within Package Limit
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Add And View DNS Slave Zones
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ View Zones Limit Per Package
 |}
 {|
@@ Line 191: / Line 222: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Add And Manage PTR Records Without DNS Zone
+|style="padding: 0px 0px 0px 30px;"|✔ Export DNS Zone To TXT File In BIND Format
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ View DNS Records Limits Per Zone
 |}
 {|
@@ Line 200: / Line 234: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Add And Manage DNS Records Sets
+|style="padding: 0px 0px 0px 30px;"|✔ Manage In Bulk
+|}
+{|
+|style="padding: 0px 0px 0px 45px;"|✔ Add/Modify/Delete/List DNS Records
+|}
+{|
+|style="padding: 0px 0px 0px 45px;"|✔ Change DNS Record Sets
+|}
+{|
+|style="padding: 0px 0px 0px 45px;"|✔ Delete Zones
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Add And Manage rDNS PTR Records Without DNS Zone
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Add, Manage And Duplicate DNS Records Sets
 |}
 {|
@@ Line 206: / Line 255: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ View Zones Limit Per Package
+|style="padding: 0px 0px 0px 30px;"|✔ Manage Zones Backups:
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ View DNS Records Limits Per Zone
+|style="padding: 0px 0px 0px 45px;"|✔ Create Manual Backups
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Create Selected Zones Backups:
+|style="padding: 0px 0px 0px 45px;"|✔ View Automated Backups
 |}
 {|
-|style="padding: 0px 0px 0px 45px;"|✔ On Server
+|style="padding: 0px 0px 0px 45px;"|✔ Restore Backups
+|}
+{|
+|style="padding: 0px 0px 0px 45px;"|✔ Preview Zones List In Created Backups
 |}
 {|
@@ Line 221: / Line 273: @@
 |}
 {|
-|style="padding: 0px 0px 10px 45px;"|✔ Import From File
+|style="padding: 0px 0px 0px 45px;"|✔ Import From File
+|}
+{|
+|style="padding: 0px 0px 10px 30px;"|✔ View Bulk Management Tasks
 |}
 *'''Automation Features:'''
@@ Line 237: / Line 292: @@
 |}
 {|
-|style="padding: 0px 0px 10px 30px;"|✔ Clear Logs
+|style="padding: 0px 0px 0px 30px;"|✔ Clear Logs
+|}
+{|
+|style="padding: 0px 0px 10px 30px;"|✔ Backup Zones
 |}
 *'''Server Settings:'''
@@ Line 282: / Line 340: @@
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ Define Record Limits Per Type
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Define Default TTL For Records
 |}
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ Define Automation Settings For Creating First Zone
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Allow To Create DNS Slave Zones
 |}
 {|
@@ Line 296: / Line 360: @@
 |}
 {|
-|style="padding: 0px 0px 10px 30px;"|✔ Toggle Client And Administrator Notifications
+|style="padding: 0px 0px 0px 30px;"|✔ Toggle Client And Administrator Notifications
+|}
+{|
+|style="padding: 0px 0px 10px 30px;"|✔ Define Allowed/Blocked IP Addresses For Zones And DNS Records Creation
 |}
 *'''Supported DNS Servers:'''
@@ Line 309: / Line 376: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Cloudflare
+|style="padding: 0px 0px 0px 30px;"|✔ BIND 9
+|}
+{|
+|style="padding: 0px 0px 00px 30px;"|✔ CentralNic Reseller (former RRPproxy)
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ Cloudflare (DNSSEC Support)
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ cPanel (DNSSEC Support)
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ cPanel & cPanel DNSOnly
+|style="padding: 0px 0px 0px 30px;"|✔ cPanel DNSOnly
 |}
 {|
@@ Line 346: / Line 422: @@
 {|
 |style="padding: 0px 0px 00px 30px;"|✔ Nettica
+|}
+{|
+|style="padding: 0px 0px 00px 30px;"|✔ Openprovider
 |}
 {|
@@ Line 355: / Line 434: @@
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ Plesk
-|}
-{|
-|style="padding: 0px 0px 0px 30px;"|✔ PowerDNS (DNSSEC Support)
 |}
 {|
@@ Line 370: / Line 446: @@
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ Rage4 DNS
-|}
-{|
-|style="padding: 0px 0px 00px 30px;"|✔ RRPProxy
 |}
 {|
@@ Line 378: / Line 451: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Simple DNS Plus V8 (DNSSEC Support)
+|style="padding: 0px 0px 0px 30px;"|✔ Simple DNS Plus V8 And V9 (DNSSEC Support)
 |}
 {|
@@ Line 398: / Line 471: @@
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ ALIAS
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ ANAME
 |}
 {|
@@ Line 419: / Line 495: @@
 {|
 |style="padding: 0px 0px 0px 30px;"|✔ HINFO
+|}
+{|
+|style="padding: 0px 0px 0px 30px;"|✔ HTTPRED
 |}
 {|
@@ Line 515: / Line 594: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Integrated With <u>IP Manager For WHMCS</u> - Complete Control And Easy Assignment Of IP Subnets [https://www.modulesgarden.com/products/whmcs/ip-manager (read more)]
+|style="padding: 0px 0px 0px 30px;"|✔ Integrated With [https://www.modulesgarden.com/products/whmcs/ip-manager IP Manager For WHMCS] - Complete Control And Easy Assignment Of IP Subnets
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Fully Integrated With [https://lagom.rsstudio.net/extensions/integrations/dns-manager-for-whmcs-by-modulesgarden Lagom] Theme
+|style="padding: 0px 0px 0px 30px;"|✔ Fully Integrated With [https://lagom.rsstudio.net/extensions/whmcs-modules-integration/dns-manager-by-modulesgarden Lagom WHMCS Client Theme]
 |}
 {|
@@ Line 524: / Line 603: @@
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Supports PHP 5.6 Up To PHP 7.3
+|style="padding: 0px 0px 0px 30px;"|✔ Supports PHP 8.1 Back To PHP 7.4
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Supports WHMCS Template Six
+|style="padding: 0px 0px 0px 30px;"|✔ Supports WHMCS Themes "Six", "Twenty-One" And "Croster"
 |}
 {|
-|style="padding: 0px 0px 0px 30px;"|✔ Supports WHMCS V7.6 And Later
+|style="padding: 0px 0px 0px 30px;"|✔ Supports WHMCS V8.9 Back To WHMCS V8.6
 |}
 {|
-|style="padding: 0px 0px 30px 30px;"|✔ Easy Module Upgrade To [https://www.modulesgarden.com/products/whmcs/dns-manager#open-source-version Open Source Version]
+|style="padding: 0px 0px 0px 30px;"|✔ Requires ionCube Loader V12 Or Later
+|}
+{|
+|style="padding: 0px 0px 30px 30px;"|✔ Easy [https://www.docs.modulesgarden.com/How_To_Upgrade_WHMCS_Module Module Upgrade] To [https://www.modulesgarden.com/products/whmcs/dns-manager#open-source-version Open Source Version]
 |}
@@ Line 545: / Line 627: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_1.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''2. In the downloaded file you might find one or two packages that support different PHP versions.'''<br/>
+|style="padding: 0px 0px 15px 15px;"|'''2. Extract the package and upload its content into the main WHMCS directory. <br/>
-In the most recent versions of the module, you will find only one package that supports PHP 7.1 and later.<br/> If you need a package for the previous versions of PHP, please [https://www.modulesgarden.com/support/ticket/general-support contact our support].
+The content of the package to upload should look like this.
-|}
-{|
-|style="padding: 0px 0px 20px 25px;"|[[File:PHP71_73.png]]
-|}
-{|
-|style="padding: 0px 0px 15px 15px;"|'''Previous updates of the module may contain two packages dedicated to various PHP versions.'''<br/>
-The first one that supports PHP 5.6 up to PHP 7.0, and the second one addressed to PHP 7.1 up to PHP 7.3.<br/>
-'''''Note:''' Keep in mind that PHP versions 5.6 up to 7.0 are no longer officially supported and their security issues are not fixed or released any more. Find more info [http://php.net/supported-versions.php here].''
-|}
-{|
-|style="padding: 0px 0px 20px 25px;"|[[File:PHP56_73.png]]
-|}
-{|
-|style="padding: 0px 0px 10px 15px;"|'' '''Important''': This situation does not affect [https://www.modulesgarden.com/products/whmcs/dns-manager#open-source-version '''the open source version'''] of this module which can be applied to any PHP from version 5.6 and later.''<br/>'' '''Note''': You can check the current PHP version in your WHMCS. To do so, proceed to ''' 'Utilities' → 'System' → 'PHP Info'.'''
-|}
-{|
-|style="padding: 0px 0px 15px 15px;"|'''3. Once you have chosen the package with the right PHP version, extract it and upload its content into the main WHMCS directory.'''<br />
-The content of the chosen PHP version files to upload should look like this.
 |}
 {|
@@ Line 573: / Line 637: @@
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''4. When you install DNS Manager For WHMCS for the first time you have to rename the '' 'license_RENAME.php' '' file.'''<br />
+|style="padding: 0px 0px 15px 15px;"|'''3. When you install DNS Manager For WHMCS for the first time you have to rename the '' 'license_RENAME.php' '' file.'''<br />
 This file is located in '' 'modules/addons/dns_manager/license_RENAME.php.' '' Rename it from '' 'license_RENAME.php' '' to '' 'license.php'. ''
 |}
@@ Line 580: / Line 644: @@
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''5. In order to configure your license key you have to edit the previously renamed '' 'license.php' '' file.'''<br />
+|style="padding: 0px 0px 15px 15px;"|'''4. In order to configure your license key you have to edit the previously renamed '' 'license.php' '' file.'''<br />
 Enter your license key between quotation marks as presented on the following screen. You can find your license key in our client area → '' 'My Products'. ''
 |}
 {|
 |style="padding: 0px 0px 20px 25px;"|[[File:DNS4.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''5. In the next step, set up the  '' 'storage' '' folder as recursively writable.'''<br />
+This folder is available at '' 'your_whmcs/modules/addons/DNSManager3/storage' ''.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_2.png]]
 |}
 {|
 |style="padding: 0px 0px 15px 15px;"|'''6. Now you have to activate the module in your WHMCS system.'''<br />
-Log in to your WHMCS admin area. Click '' 'Setup' '' then choose '' 'Addon Modules'. ''<br />
+Go to '' 'WHMCS Admin Area' '' → '' 'System Settings' '' → '' 'Addon Modules' ''. Afterwards, find '' 'DNS Manager' '' and '' 'DNS Manager v3' '' and activate both addons.
-Afterward, find '' 'DNS Manager' '' and press the '' 'Activate' '' button.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_3.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_3.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|'''7. In the next step you need to permit access to this module. To do so click on the '' 'Configure' '' button, choose '' 'Full Administrator' '' and press '' 'Save Changes'.'' '''
+|style="padding: 0px 0px 20px 15px;"|'''7. In the next step you need to permit access to this module. To do so click on the '' 'Configure' '' button, choose '' 'Full Administrator' '' and press '' 'Save Changes'.'' '''<br/>
+Remember to repeat this action for both addons.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_4.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_4.png]]
 |}
 {|
@@ Line 609: / Line 680: @@
 =Configuration and Management=
 {|
-|style="padding: 10px 0px 30px 15px;"|This section has been divided into two main parts to allow full and, at the same time, easy understanding of the whole module functionality.<br/>In the first part '' 'Basic Configuration' '' an exemplary flow of basic configuration of servers, through creating packages and then zones management<br/> from both the client and the administrator side has been presented.<br/> In the second part, there are described additional settings and tools that can be used while working with DNS Manager For WHMCS.
+|style="padding: 10px 0px 15px 15px;"|If the current version of your module is 3.0 and later, you have access to both DNS Manager and DNS Manager v3 addons.<br/> Please note that most of the module management is already located under the '''DNS Manager V3''' addon, yet some sections are still available under DNS Manager only.<br/> Please navigate to ''Addons → DNS Manager V3'' and follow the below described steps to configure and manage your module successfully, if required, navigate to DNS Manager addon.
 |}
-==Basic Configuration==
 {|
-|style="padding: 10px 0px 15px 15px;"|In the first place we would like to show you the process of configuring your DNS manager on a simple example.<br/>Follow the steps below to see how the process looks like in practice.<br />
+|style="padding: 0px 0px 30px 15px;"|This section has been divided into two main parts to allow full and, at the same time, easy understanding of the whole module functionality.<br/>In the first part '' 'Basic Configuration' '' an exemplary flow of basic configuration of servers, through creating packages and then zones management<br/> from both the client and the administrator side has been presented.<br/> In the second part, there are described additional settings and tools that can be used while working with DNS Manager For WHMCS.
-Proceed to  '' 'Addons' → 'DNS Manager'. '' There are several sections, but the one that you should be interested in the most in the beginning is named '' 'Servers'. ''<br/> You will find it under the '' 'Settings' '' tab.
 |}
+==Basic Configuration==
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS2_6_1.png]]
+|style="padding: 10px 0px 15px 15px;"|In the first place we would like to show you the process of configuring your DNS manager on a simple example.<br/>Follow the steps below to see how the process looks like in practice.<br />
+Proceed to  '' 'Addons' → 'DNS Manager V3'. '' There are several sections, but the one that you should be interested in the most in the beginning is named '' 'Servers'. ''<br/> You will find it under the '' 'Settings' '' tab.
 |}
 ===Servers Configuration===
@@ Line 624: / Line 695: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_7.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_7.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|To add a new server you must fill out some data to allow connection with it. As an example, we will try to connect with cPanel server.<br/>Additionally, you may declare here whether you need rDNS, Multiple PTR or Cashe. Select the desired options.<br/><br/>
+|style="padding: 0px 0px 15px 15px;"|To add a new server you must fill out some data to allow connection with it. As an example, we will try to connect with cPanel server.<br/>Additionally, you may declare here whether you need rDNS, Multiple PTR or Cache. Select the desired options.<br/><br/>
-Please note, that there is also an option '''Enable DNSSEC''' available. However, it is currently compatible only with '''DirectAdmin, PowerDNS''' and '''PowerDNS V4''' submodules.<br/>
+Please note, that there is also an option '''Enable DNSSEC''' available. However, it is currently compatible only with '''CloudFlare, cPanel, DirectAdmin, PowerDNS V4''' and '''Simple DNS Plus V8 And V9''' submodules.<br/>
 DNSSEC ''(DNS Security Extensions)'' - allows enabling validation and authentication of the origin and integrity of DNS data.<br/> If you enable this option, the client will be allowed to turn on DNSSEC for a zone and display its DNSSEC-related details accordingly.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_8.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_8.png]]
 |}
 {|
 |style="padding: 0px 0px 15px 25px;"|If you want to have the nameserver records populated each time a new zone is created, make sure to check the ''Populate Nameservers'' option.<br/>
-A similar scenario applies to the ''Overwrite SOA record'' checkbox which stands for automatically assigned nameservers in the SOA record.
+A similar scenario applies to the ''Overwrite SOA Record'' checkbox which stands for automatically assigned nameservers in the SOA record.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_8_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_8_1.png]]
 |}
 {|
 |style="padding: 0px 0px 15px 15px;"|Once you have chosen a server from the dropdown menu, '' 'Configuration' '' and '' 'Nameservers' '' tabs appear.<br/>Enter your username, password, Hostname/IP and any other details needed to connect successfully.<br/> Now, press '' 'Nameservers' '' and enter the nameservers that will be visible for your customers in their client area. <br/>
-Before you save the changes remember to test the connection.<br/>
+Remember to save the changes when ready.<br/>
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_9.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_9.png]]
 |}
 {|
@@ Line 652: / Line 723: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_9_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_9_0.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|Now, that you have a ready server on the list of servers you may manage it. Turn it on/off, edit or delete.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_9_1.png]]
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_10.png]]
+|style="padding: 0px 0px 20px 15px;"|Now, that you have a ready servers on the list, you may manage them. Turn it on/off by changing their status ''(1.)'', edit ''(2.)'', test connection ''(3.)'' and delete ''(4.)''.
 |}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_10.png]]
+|}
+====BIND 9 Configuration====
+{|
+|style="padding: 10px 0px 15px 15px;"|DNS Manager For WHMCS offers solutions not only for remote DNS servers,  but it can also support your own DNS server created using [https://www.isc.org/bind/ BIND 9].<br/>
+'' '''Please note''' that currently DNSSEC for BIND 9 is '''not''' supported yet.''
+In this part, we will show you an exemplary BIND 9 configuration.<br/>
+Firstly, go to the '' 'Servers' '' section in the '' 'Settings' '' tab, click '' 'Add Server' '' and select '' 'Bind9' '' module.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNSBind9_1.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|Now, move to the '' 'Configuration' '' tab and provide essential data to your BIND 9 server configuration.<br/>
+The '' 'Path To Bind9 Config Directory' '' filed is used to locate the BIND 9 '' 'named.conf.local' '' configuration file.<br/>
+Please remember that all paths presented on the screens below are only an illustration and you need to adjust to directories paths on your own BIND 9 server.<br/>
+The module should also have permissions set to access these directories.<br/>
+Thanks to provided backup paths, you can also easily revert a backup copy in case of any breakdown so it is extremely important to carry out the configuration properly.<br/>
+Also, note that the module can create a large number of backup files within a newly created 'zones' directory based on the provided path.
+'' '''Important:''' Remember that paths to 'Bind9 Config Directory' and 'Backup Directory' should start with ''' / ''' and be absolute.''
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNSBind9_2.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|Another obligatory step to set up is '' 'Nameservers' ''. Fill in at least one nameserver and its IP address.<br/>
+Do not also forget to save the changes.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNSBind9_3.png]]
+|}
+{|
+|style="padding: 0px 0px 20px 15px;"|Once the configuration has been established successfully, you can test your connection, view your ready server which can be easily managed here.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNSBind9_4.png]]
+|}
+{|
 ===Management of Packages===
@@ Line 669: / Line 782: @@
 |}
 {|
-|style="padding: 0px 0px 15x 15px;"|In the '' 'General' '' section, you obviously have to name the newly created package and define the number of zones per item ''(limit of zones that a client may then create within this package).''<br/> Here, you can also decide if zones should be created automatically after defined actions.<br/> These are:
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS_11_1.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''1.''' In the '' 'General' '' section you have to:
+* name the newly created package
+* define the number of zones per item ''(limit of zones that a client may then create within this package)''
+<div id="Master_Slave_Zones"></div>
+* decide if you allow creating slave zones<br/> '''Important:''' The module allows the creation of two types of DNS zones, master and slave ones:<br/>  '''''Primary (Master) DNS zones''''' – it is a holder of the original zone file (all the DNS records for the zone). You can manage a host through this zone.<br/> '''''Secondary (Slave) DNS zone''''' – it holds a copy of the zone file. You can use them for better performance, for hiding your primary zones, for backups and redundancy.<br/>
+'''2.''' Here, you can also decide if zones should be created automatically after defined actions.<br/> These are:
 *'''New Item''' - zones will be created automatically for every new product being activated
-*'''Pending Transfer Domain''' - zones will be automatically created for the domains during their transfer:
+*'''Pending Domain Transfer''' - zones will be automatically created for the domains during their transfer:
-**''Pre'' - a new zone will be created right before launching the transfer to the registrar
+**''Before'' - a new zone will be created right before launching the transfer to the registrar
 **''After'' - the transfer occurs first, and only if it ends successfully a new zone is created
-*'''Pending Registration Domain''' - zones will be created automatically for newly registered domains
+*'''Pending Domain Registration ''' - zones will be created automatically for newly registered domains
+**''Before'' - a new zone will be created shortly before sending a registration request to the registrar
+**''After'' - a new zone will be created once the status of registration request is received from the registrar
 *'''Domain with DNS Management''' - zones will be created automatically for domains that have been ordered with the 'DNS Management' domain addon
-*'''Allow Update Of Existing Zone''' - if a zone already exists, it will be updated with newly added record sets
+*'''Existing Zone Update''' - if a zone already exists, it will be updated with newly added record sets<br/>
+'''3.''' Define the maximum, allowed '''limit of records.'''<br/>
+'''4.''' Choose [[#DNS_Record_Sets|DNS Record Sets]] that will be applied to this package.
+*'''Default DNS Record Set''' - this default set will be automatically applied upon the zone creation
+*'''DNS Record Sets''' - choose the sets created by the administrator that will also be available for clients to choose from when adding a new zone
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_12.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_12.png]]
 |}
 ====Items====
@@ Line 687: / Line 817: @@
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_13.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_13.png]]
 |}
@@ Line 693: / Line 823: @@
 {|
 |style="padding: 10px 0px 15px 15px;"|Assign the package to the previously added server.<br/>
-''Note: You may always assign the package to more than one server.''
+''Note: You may always assign the package to more than one server.'' <br/> Due to extra synchronization, you may select which server will be marked as '' 'Master Server'' '.<br/> As a result, once you modify the '' 'Master Server' '' and run cron commands, all performed changes (such as adding, deleting new records etc.) will be implemented to other servers as well.  <br/>
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_14.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_14.png]]
 |}
-====Record====
+====Records====
 {|
 |style="padding: 10px 0px 15px 15px;"|In this part, you may define the record types that you want to enable and declare their limit.
@@ Line 704: / Line 835: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_15.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_15.png]]
 |}
+====Notifications====
 {|
-|style="padding: 10px 0px 15px 15px;"|You may also choose [[#DNS Records Sets|DNS Records Sets]] that will be applied to this package.
+|style="padding: 10px 0px 20px 15px;"|Here, you may configure which notification will be sent to clients and administrators.
-*'''Default DNS Record Set''' - this default set will be automatically applied upon the zone creation
-*'''DNS Record Sets''' - choose the sets created by the administrator that will also be available for clients to choose from when adding a new zone
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_15_0.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_16.png]]
 |}
@@ Line 720: / Line 851: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_15_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_15_1.png]]
 |}
 {|
@@ Line 726: / Line 857: @@
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_15_2.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS30_15_2.png]]
 |}
-====Notification====
+====IP Management====
 {|
-|style="padding: 10px 0px 20px 15px;"|In the last part, you may configure which notification will be sent to clients and administrators.<br/> Do not forget to '' 'Add' '' the package.
+|style="padding: 10px 0px 15px 15px;"|In the last part, you can specify which IP addresses can be used by your clients while creating a package. If you do not provide anything, clients can use any IP addresses without any limitations.<br/> The '' 'IP Addresses Blacklist' '' section allows you to ban IP addresses. This will prevent users from using specified IP addresses.<br/>
+Remember to save the changes when the package configuration is ready.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_16.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_16_1.png]]
 |}
 {|
@@ Line 740: / Line 872: @@
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_17.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_17.png]]
 |}
+==Client Area==
+{|
+|style="padding: 10px 0px 15px 15px;"|In order to take advantage of the brand new management page in the client area, you need to allow access in the DNS Manager v3 addon. <br/>Navigate to ''Addons → DNS Manager v3 → Settings → Global Settings,'' and enable '' 'DNS Management Link.' '' This will enable a '' 'Manage DNS' '' button in the Client Area.
+|}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_0.png]]
+|}
+{|
+|style="padding: 00px 0px 15px 15px;"|Next navigate to ''Addons → DNS Manager v3 → Settings → General.'' There you will find two sections: '' 'Cron task' '' and '' 'Module Settings'.''<br/>
+*'''Cron Task''' - set up this cron task in order to successfully run tasks added in the '' 'Bulk Management' '' section in the client area. We recommend setting up a 5 minutes interval:
+ php -q /home/your_whmcs/modules/addons/DNSManager3/cron/cron.php queue
+*'''Module Settings''' - enable to overwrite the DNS Manager v2 link of the client area<br/>
+'''''Note:''' If you do not enable this option, your clients will still have access to the previous view of the '' 'Manage DNS' '' page, still available for [https://www.docs.modulesgarden.com/DNS_Manager_For_WHMCS#DNS_Management_in_Client_Area  DNS Manager v2.x.x] users.''
+|}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_0.png]]
+|}
 ===DNS Management in Client Area===
 {|
@@ Line 748: / Line 898: @@
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS2_18.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS30_1.png]]
 |}
-====New Zones====
+====Zones====
 {|
 |style="padding: 10px 0px 15px 15px;"|In here, clients may add new zones. To do so, simply type in the name of the zone and choose IP address from the available or enter your custom IP.<br/>It depends on your configuration - read more about possible options [[#Other|here]].<br/>From the dropdown menu clients can also define record sets. If they do not have any added, the default one created by the administrator in the admin area will be selected.<br/>When clients create sets by themselves, they can use the one defined by them as default, or choose other one from the list.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_19.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_2.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_19_1.png]]
+|style="padding: 0px 0px 20px 15px;"|Standard list view of DNS Zones:<br/>
+'''''Note:''' You can turn on this mode in the 'DNS Manager v3 addon' → 'Settings' → 'Global Settings' → 'Other' → [[#Other|'Zones Single Table View']].''
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_30_0.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|The module gives you the possibility of creating two types of zones. These are master zones and slave zones. For more info please read [[#Master_Slave_Zones|this section]].<br/>
+Form to create a master DNS zone:
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_3.png]]
+|}
+{|
+|style="padding: 0px 0px 20px 15px;"|If you wish to create a slave zone, this is how the form will look like:
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_30_5.png]]
 |}
 {|
 |style="padding: 0px 0px 15px 15px;"|Allowed actions on a zone:
-*edit existing zone
+*edit an existing zone
 *delete zone
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_20.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_4.png]]
 |}
 {|
@@ Line 772: / Line 939: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_45.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_5.png]]
 |}
 {|
@@ Line 778: / Line 945: @@
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS2_46.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_6.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|In the case of slave zones, press the dedicated icon '''(2.)''' to only view the zone records list.<br/>
+You may force the slave zone to refresh by pressing the button '''(1.)''' - related to slave zones on servers other than PowerDNSv4.<br/> A new task will be added to the queue and the zone will be refreshed with the setup [[#Slave_Zones|time interval]].
+|}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS30_6_1.png]]
 |}
+=====DNSSEC=====
+{|
+|style="padding: 10px 0px 15px 15px;"|If the '' 'Enable DNSSEC' '' option has been selected ''('CloudFlare', 'cPanel', 'DirectAdmin', 'PowerDNS', 'PowerDNS V4' and 'Simple DNS Plus V8 And V9' submodules),'' the client may turn it on. <br/>
+To do so, navigate to '' 'Additional Actions' → 'DNSSEC'.''
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_7.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|Enable DNSSEC here, you will then get access to DNNSSEC details for the zone, including keys and delegation signer records.<br/>
+Press '' 'Rectify Zone' '' to comply with DNSSEC.
+|}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS30_8.png]]
+|}
+====Bulk Management====
+{|
+|style="padding: 10px 0px 15px 15px;"|Under this section you may manage numerous DNS zones. Select at least one zone on the list and press the '' 'Choose Action' '' button. <br/> There are six allowed actions that can be preformed on zones. <br/>
+Allowed actions:
+*Add Record
+*Modify Record
+*Delete Record
+*List Records
+*Change Record Set
+*Delete Zones
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_9.png]]
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_10.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''Add Record''' - define the newly created record type, name, TTL and address.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_11.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''List Records''' - search for records manually by typing in exactly what you need or enable '' 'Regular Expression' '' to broaden your search results. <br/> Use regex syntax, for example:
+* '''/abc/''' - all records including "abc" string ''(lower case only)''
+* '''/[\d]+/''' - all records including numbers
+* '''/^www/''' - all records that start with "www" ''(lower case only)''
+* '''/\.com$/''' - all records that end with ".com" ''(lower case only)''
+* '''/[abc]/i''' - all records that include "a," "b" or "c" letters ''(lower or capital case, any position)''
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_14.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''Modify Record''' - you may modify existing records. Search for records manually by typing in exactly what you need or enable '' 'Regular Expression' '' to broaden your search results. <br/> Use regex syntax, for example: <br/>
+Search: '''/(\d+)abc/i''' <br/>
+Replace With: '''def$1'''<br/>
+The above example will result in exchanging all records that include a string of numbers followed by ''abc'' letters to a '' 'def' '' phrase with the same string of numbers:<br/>
+ phrase2137abc → phrase'''def'''2137
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_12.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''Delete Record''' - select the record type and specify which records shall be deleted. Enter specific data or use regular expression.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_13.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''Change Record Set''' - choose a new record set. You may enable the '' 'Wipe Records' '' option to clear the selected zone at the same time.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS30_13_2.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''Delete Zones''' - remove all the selected DNS zones.
+|}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS30_13_3.png]]
+|}
+<!-- nie znalazłam tej opcji w DNS3
 ====Enable DNSSEC====
 {|
@@ Line 796: / Line 1,050: @@
 |style="padding: 0px 0px 30px 25px;"|[[File:DNS2_45_3.png]]
 |}
+-->
-====Add rDNS Records====
+====rDNS====
-{|
-|style="padding: 10px 0px 15px 15px;"|If you have allowed the rDNS management in the client area by selecting either '' 'Allow DNS And rDNS Management' '' or '' 'Allow Only rDNS Management' '' option (read more [[#Other|here]]) in  global settings,<br/> your clients can create PTR records for IPv4 and IPv6 addresses without any related zone. To do so, press '' 'Manage Reverse DNS'. ''
-|}
-{|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_63.png]]
-|}
 {|
-|style="padding: 0px 0px 20px 15px;"|Find and press the '' 'Add PTR' '' button.
+|style="padding: 10px 0px 15px 15px;"|If you have allowed the rDNS management in the client area by selecting either '' 'Allow DNS And rDNS Management' '' or '' 'Allow Only rDNS Management' '' option (read more [[#Other|here]]) in  global settings,<br/> your clients can create PTR records for IPv4 and IPv6 addresses without any related zone. To do so, press '' 'Add PTR Record'. ''
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_64.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_50.png]]
 |}
 {|
@@ Line 815: / Line 1,064: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_65.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_51.png]]
 |}
 {|
@@ Line 821: / Line 1,070: @@
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS2_66.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_52.png]]
 |}
-====Add DNS Record Sets====
+====Record Sets====
 {|
 |style="padding: 10px 0px 20px 15px;"|You can add and manage records sets in the '' 'DNS Record Sets' '' section as shown below.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_10.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_53.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|Click the '' 'Add Set' '' button and provide the necessary details.<br/>It can be also set as default.
+|style="padding: 0px 0px 20px 15px;"|Click the '' 'Add Record Set' '' button and provide the necessary details.<br/>It can be also set as default.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_11.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_55.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_12.png]]
+|style="padding: 0px 0px 20px 15px;"|Your newly created DNS record should appear on the list. You may edit the record set, edit general record set data, duplicate or delete it completely.
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|You newly created DNS record should appear on the list. You may edit or delete it completely.
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_56.png]]
-|}
-{|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_13.png]]
 |}
 ====Backups====
 {|
-|style="padding: 10px 0px 15px 15px;"|You can manage fully your zones backups. Move to the mentioned section to see any options.<br/>
+|style="padding: 10px 0px 15px 15px;"|'''Backup Tasks''' <br/>
-Note that this option must have been previously allowed by your administrator in general settings.
+You can manage fully your zones backups. Move to the mentioned section to see any options.<br/>
+Note that this option must have been previously allowed by your administrator in general settings. Press the '' 'Create Backup' '' button to start.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_15.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_57.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|There are two sections available. Current "Backups Tasks" and a "Backups List" including files with backed up zones.<br/>
+|style="padding: 0px 0px 15px 15px;"|A new task is added immediately. Now, all you need to do is edit the added backup task and there select the zones from available that will be processed and stored in a backup file.<br/>
-Press the '' 'Create Backup' '' button to start.
+Press the '' 'Create Zones Backup' '' button when ready.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_16.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_58.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|A new task is added immediately. Now, all you need to do is select the zones from available that will be processed and stored in a backup file.<br/>
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_59.png]]
-Press the '' 'Backup Zones' '' button when ready.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_17.png]]
+|style="padding: 0px 0px 15px 15px;"|The just added task to back up the zones is now visible on the list of all tasks. There are also information on the task progress and number of zones already processed.<br/>
-|}
-{|
-|style="padding: 0px 0px 15px 15px;"|'''Backups Tasks'''<br/>
-The just added task to back up the zones is now visible on the list of all tasks. There are also information on the task progress and number of zones already processed.<br/>
 To see details, press '' 'Show List' '' button. <br/>
 '''''Important:''' Keep in mind that you must wait until the next execution of the "Cron Importer" to start processing. If it is set to more than 5 minutes, you will not see the results on the run.''
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_18.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_60.png]]
-|}
-{|
-|style="padding: 0px 0px 20px 15px;"|You will be moved to the list of currently maintained zones. Check the status of each one of them.
-|}
-{|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_19.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''Backups List'''<br/>
+|style="padding: 0px 0px 15px 15px;"|'''Manual Backups List'''<br/>
 Here you will find a list of all files with a number of backed up zones. In order to upload a ready backup file, simply press the '' 'Upload File' '' button.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_20.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_62.png]]
 |}
 {|
@@ Line 895: / Line 1,131: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_21.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_63.png]]
 |}
 {|
 |style="padding: 0px 0px 15px 15px;"|Use the action buttons to start the tasks:<br/>
-'''1.''' - Restore backup file. This action, when stared, is also visible on the list of tasks above.<br/>
+'''1.''' - Show Backup File Content<br/>
 '''2.''' - Download the file.<br/>
-'''3.''' - Delete the file.
+'''3.''' - Restore backup file. This action, when stared, is also visible on the list of tasks above.<br/>
+'''4.''' - Delete the file.
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_22.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_64.png]]
+|}
+====Tasks====
+{|
+|style="padding: 10px 0px 20px 15px;"|You will find a list of current tasks in '' 'Tasks' '' section.<br/> Among all tasks there are import tasks, migration and synchronization tasks.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_65.png]]
+|}
+{|
+|style="padding: 0px 0px 30px 15px;"|According to specifically set-up cron jobs all created tasks are regularly executed. Here, you can see the current status of each task.<br/> If it is queuing for the next cron run, is currently executed, aborted or complete. Check when they were executed for the last time ''(Last Execution)'' and when the task was added. <br/>Available actions: call execution manually and remove the task.
 |}
@@ Line 912: / Line 1,160: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_21.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_21.png]]
 |}
 {|
@@ Line 919: / Line 1,167: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_121.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_121.png]]
 |}
 {|
@@ Line 925: / Line 1,173: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_122.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_122.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"| Note that both the admin and client area allow the user to apply a record set to a single or to multiple zones.
+|style="padding: 0px 0px 20px 15px;"| If you select a service that is in a package with the allowed option to create slave zones, a dedicated switcher will appear.<br/>
+'''''Important:''' The module may create two types of zones, master and slave ones. ''Master'' type zones are created on DNS servers and the records are synchronized via AXFR protocol by itself.<br/> In the case of slave zones, the module creates a slave zone on DNS servers and that is the DNS server that performs the synchronization. <br/>("PowerDNSV4" only, in the case of other servers like "cPanel", you have to manually force the synchronization).''
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_122_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_122_0.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_122_2.png]]
+|style="padding: 0px 0px 20px 15px;"| Note that both the admin and client area allow the user to apply a record set to a single or to multiple zones.
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|If you wish to wipe the selected zone at the same time, make sure to tick the '' 'Wipe Records' ''  option.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_122_1.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_122_3.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_66.png]]
 |}
 {|
 |style="padding: 0px 0px 15px 15px;"|Actions on zones from the admin area:
-*change related item - choose one of available items from a dropdown menu and save changes
+#Change Related Item - choose one of the available items from a dropdown menu and save changes
-*edit zone - modify existing records or add new ones
+#Edit DNS Zone Records- modify existing records or add new ones
-*create - use this button to create a zone on the server
+#Add DNS Zone - use this button to create a zone on the server
-*import - choose a file from which zones will be imported
+#Import DNS Zone From File - choose a file from which zones will be imported
-*export - choose a file to which zones will be exported
+#Export DNS Zone To File - choose a file to which zones will be exported
-*delete - if you use this button, the zone will be deleted both from WHMCS and from the server
+#Export DNS Zone To TXT File In BIND Format - a TXT file will be saved just after pressing the button
-*remove from WHMCS - zone will still be available on the server
+#Lock/Unlock DNS Zone - if you lock a zone, it will not be possible to edit this zone in the client area
+#Delete DNS Zone - if you use this button, the zone will be deleted both from WHMCS and from the server
+#Remove DNS Zone From WHMCS - zone will still be available on the server
+#Refresh Slave Zone - press this button to manually add the task to the queue and force refreshing a slave zone via AXFR protocol ''(slave zones created on servers other than PowerDNSv4)''
+#View DNS Zone - press to see a list of records; you may also refresh the slave zone from this level ''(slave zones only)''
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_22.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_22.png]]
 |}
 ==Additional Tools==
-===DNS Record Sets===
+===Settings===
 {|
-|style="padding: 10px 0px 20px 15px;"|Create ready made sets of DNS records. You will find them in '' 'Settings' → 'DNS Records Sets'. '' <br/>Press '' 'Add Set' '' to create a new one.
+|style="padding: 10px 0px 20px 15px;"|Remember that if you want to redirect your clients to DNS Management page in V3.0, you must previously configure the dedicated addon settings.<br/>Move to ''Addons → DNS Manager v3 → Settings → General.'' There you will find cron task that you will need to execute in order to allow bulk actions on zones in the client area to be performed.<br/>
+Furthermore, in order to redirect your client to a brand new client area page of the DNS Manager v3.0, please enable the option to overwrite the client area link.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_23.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_0.png]]
 |}
+===Global Settings===
 {|
-|style="padding: 0px 0px 20px 15px;"|Enter the newly created set name and then choose records from the dropdown menu, press '' '+'. ''
+|style="padding: 10px 0px 20px 15px;"|This section has been designed to allow quick and simple configuration of global settings from one place.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_24.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_27.png]]
 |}
+====Templates====
 {|
-|style="padding: 0px 0px 15px 15px;"|Now, fill out the data as required.<br/>
+|style="padding: 10px 0px 15px 15px;"|Choose a default template that will be used in the client area.<br/>
-'' '''Note:''' You may add adequate variables for domain and IP address and then these fields will be automatically changed to domain/zone IP when this record set is used.<br/>
+If you have more than one template then you may allow your clients switch between them.<br/>
-For example, if you have the '' 'example.com' '' domain with '' '123.123.123.123' '' IP address all you have to do is add the following variable to the DNS Record Set:''<br/>
+Decide whether you wish to use a ready-configured redirection to the DNS Management page in the client area.
-* '' '''{$domain}''' '' - will return full '' 'example.com' '' domain address
-* '' '''{$domainname}''' '' - will return only '' 'example' '' name
-* '' '''{$domainextension}''' '' -  will return '' 'com' '' extension
-*  '' '''{$ip}''' '' will return the '' '123.123.123.123' '' IP address; that can be:
-** IP address assigned to the domain by a client, provided while creating a zone
-** hosting dedicated IP address
-** WHMCS server address provided it is a hosting
-* '' '''{$serverhostname}''' '' - will return the DNS server address or its IP address, depending which one has been provided in the module's DNS server configuration in the admin area,<br/> e.g.: ''yourdnsserver.com'' or ''12.23.34.45''
-* '' '''{$ns1}''', '''{$ns2}''', '''{$ns3}''', '''{$ns4}''' '' and '' '''{$ns5}''' '' - will return the global nameservers addresses specified in the order basing on the sequential number of the corresponding data in the variables
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_25.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_28.png]]
 |}
+====Logs And Notifications====
 {|
-|style="padding: 0px 0px 15px 15px;"|Created DNS Records Sets can be then used while preparing ready packages, as it was described. <br/>Ready made sets allow much faster and more personal configuration of packages.
+|style="padding: 10px 0px 15px 15px;"|In this part, you may impose when log entries and notifications should be removed from the system database. <br/>If you wish you may also check the '' 'Log Successful Actions' '' option to store all entries in logs ''(DNS Manager → Settings → Logs).''<br/> '' 'Log Zone Actions' '' - select single actions on zones, logs on them will be stored in the module as well.
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_26.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_32.png]]
+|}
+====Slave Zones====
+{|
+|style="padding: 10px 0px 15px 15px;"|The following section is dedicated to the created in the module slave zones on servers other than PowerDNSv4 ''(in its case, the slave zones are refreshed automatically).''
+Here, you may define the time interval at which the slave zones will be refreshed and their information synchronized with a remote DNS master server using the AXFR protocol.<br/> Note that the time is measured in hours.
+|}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_33_1.png]]
 |}
-===Global Settings===
+====Other====
 {|
-|style="padding: 10px 0px 20px 15px;"|This section has been designed to allow quick and simple configuration of global settings from one place.
+|style="padding: 10px 0px 15px 15px;"|The box with '' 'Other' '' options available is a crucial part of configuration where you can manage [[#IP Manager For WHMCS Integration|IP Manager For WHMCS]] module and manage PTR records creation. <br/>Besides, here you can switch off the guide with simple instructions visible on the dashboard.
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_27.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_62.png]]
 |}
-====Templates====
 {|
-|style="padding: 10px 0px 15px 15px;"|Choose a default template that will be used in the client area.<br/>
+|style="padding: 0px 0px 15px 15px;"|'''1. Client Area Management''' - depending on the configuration, the client has access to:<br/>
-If you have more than one template then you may allow your clients switch between them.<br/>
+*'''DNS And rDNS Management''' -  give your clients full access to DNS management in the client area.
-Decide whether you wish to use a ready-configured redirection to the DNS Management page in the client area.
+*'''rDNS Management Only''' - create PTR records for IPv4 and IPv6 addresses without a related zone.<br/> If this option is enabled your clients will be only allowed to add reverse DNS with no zone related. Other sections are blocked
+*'''DNS Management Only''' - the '' 'rDNS' '' tab will be blocked for the client
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS2_28.png]]
+|style="padding: 0px 0px 20px 15px;"|'''2. Domain/Product/Addon/Other Item Options''' - restrict clients to manually create zones using the indicated domains only.<br/>
+*''Allow Only That Domain''
+*''Allow Only That Product Domain''
+*''Allow Only Domains From Domains Items''
+*''Allow Only Domains From Product Items''
+*''Allow Only Domains From Domains And Product Items''
+*''Allow Custom Domain''
 |}
-====Notifications====
 {|
-|style="padding: 10px 0px 15px 15px;"|In this part, set which notification should be sent to clients and which to the administrator. Select the ones that interest you.<br/>
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_67_1.png]]
-Press '' 'Modify' '' and you will be quickly redirected to the email template page where you can adjust it to your needs.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_29.png]]
+|style="padding: 0px 0px 20px 15px;"|'''3. Exclude Used Zones From Zone Creation''' - select to exclude the already used domains from the possibility of being used again in a newly added zone
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|Use the '' 'Exclude' '' button to specify domains, products and addons that the zones assigned to them will NOT be included in notifications.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_67_3.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_30.png]]
+|style="padding: 0px 0px 15px 15px;"|'''4. Related Service IP Addresses Only''' - create zones and PTR records with a related IP address only.<br/> When adding a new zone/PTR record you can choose from available hosting related IP addresses only as marked on the screen below.
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|Use the '' 'Include' '' button to specify which admin users will receive notifications.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_67_0.png]]
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_31.png]]
+|style="padding: 0px 0px 15px 15px;"|'''5. Custom Subnet IP Address''' - create zones and PTR records with an IP address included in a subnet related to the product. <br/>
+'''''Note:''' This option works only if you have integrated your DNS Manager with [https://www.modulesgarden.com/products/whmcs/ip-manager IP Manager For WHMCS].''
 |}
-====Client Area Zones Status====
 {|
-|style="padding: 10px 0px 20px 15px;"| Checking the selected boxes will result in an additional status concerning a given domain in the client area.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_67_1.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS31_1.png]]
+|style="padding: 0px 0px 15px 15px;"|'''5. rDNS Custom IP Address''' - create PTR records with a custom IP, enter a new IP address to create a new PTR.<br/> '''''Note:''' Both IPv4 and IPv6 are supported by DNS Manager For WHMCS.''
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"| Pressing the ''Modify'' button next to a given option will cause a new window to appear where you can set up your own custom status by means of HTML.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_68_1.png]]
-Your new description can include the ''{$domain}'' variable which will give the domain address back in the status message.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS31_2.png]]
+|style="padding: 0px 0px 15px 15px;"|'''6. Custom IP Address''' - create zones with a custom IP address. If you have no IP addresses to choose from, you have to enter a new IP address.<br/> '''''Note:''' Both IPv4 and IPv6 are supported by DNS Manager For WHMCS.''
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"| You can see an example status on the screen below.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_67_2.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS31_3.png]]
+|style="padding: 0px 0px 20px 15px;"|'''7. Client Area Record Sets''' - clients may manage DNS records sets.
 |}
-====Logs And Notifications====
 {|
-|style="padding: 10px 0px 15px 15px;"|In this part you may impose when log entries and notifications should be removed from the system database. <br/>If you wish you may also check the '' 'Log Successful Actions' '' option to store all entries in logs ''(DNS Manager → Settings → Logs).''<br/> '' 'Log Zone Actions' '' - select single actions on zones, logs on them will be stored in the module as well.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_69_1.png]]
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS2_32.png]]
+|style="padding: 0px 0px 15px 15px;"|'''8. Client Area Backups''' and '''Client Area Backups Limit''' - clients are given the option to create backups of their zones and upload backup files. <br/> It is advised to set a limit on the number of allowed backups. Default '' '-1' ''  indicates ''unlimited''
 |}
-====Other====
 {|
-|style="padding: 10px 0px 15px 15px;"|The box with '' 'Other' '' options available is a crucial part of configuration where you can manage IP Manager For WHMCS  [[#IP Manager For WHMCS Integration|IP Manager For WHMCS integration]] module and manage PTR records creation. <br/>Besides, here you can switch off the guide with simple instructions visible on dashboard.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_69_2.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_62.png]]
+|style="padding: 0px 0px 10px 15px;"|'''9. Protect Zones On Product Termination''' - zones are not automatically deleted once the product has been terminated.
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''1. Client Area Management''' - depending on the configuration, the client has access to:<br/>
+|style="padding: 0px 0px 20px 15px;"|'''10. Show Product Name''' - a full product name is shown, instead of the general type with an order number.
-*DNS And rDNS Management
-*rDNS Management Only
-*DNS Management Only
-<br/>
-''rDNS Management Only'' - create PTR records for IPv4 and IPv6 addresses without a related zone.<br/> If this option is enabled your clients will be allowed to add reverse DNS with no zone related. To do so proceed to '' 'Manage DNS' → 'Manage Reverse DNS' '' in your client area.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_66_2.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_69_4.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|''DNS Management Only'' - add and edit existing DNS zones.
+|style="padding: 0px 0px 20px 15px;"|'''11. Show Nameservers''' - submodule nameservers will be displayed in the '' 'Edit Zone' ''section of the client area.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_66_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_69_5.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|''DNS And rDNS Management'' - give your clients full access to DNS management in the client area.
+|style="padding: 0px 0px 20px 15px;"|'''12. Show DNS Manager Button''' - the '' 'DNS Manager' '' button will show up in the sidebar section of products which have zones created. <br/> Thanks to this button you can easily move to the '' 'Edit Zone' '' section.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_66_3.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_69_6.png]]
 |}
+====Notifications====
 {|
-|style="padding: 0px 0px 20px 15px;"|'''2. Domain/Product/Addon/Other Item Options''' - restrict clients to manually create zones using the indicated domains only.<br/>
+|style="padding: 10px 0px 15px 15px;"|In this part, set which notification should be sent to clients and which to the administrator. Select the ones that interest you.<br/>
-*''Allow Only That Domain''
+Press '' 'Modify' '' and you will be quickly redirected to the email template page where you can adjust it to your needs.
-*''Allow Only That Product Domain''
-*''Allow Only Domains From Domains Items''
-*''Allow Only Domains From Product Items''
-*''Allow Only Domains From Domains And Product Items''
-*''Allow Custom Domain''
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_67_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_29.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|'''3. Exclude Used Zones From Zone Cration''' - select to exclude the already used domains from the possibility to be used again in a newly added zone
+|style="padding: 0px 0px 20px 15px;"|Use the '' 'Exclude' '' button to specify domains, products and addons that the zones assigned to them will NOT be included in notifications.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_67_3.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_30.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''4. Related Service IP Addresses Only''' - create zones and PTR records with a related IP address only.<br/> When adding a new zone/PTR record you can choose from available hosting related IP addresses only as marked on the screen below.
+|style="padding: 0px 0px 20px 15px;"|Use the '' 'Include' '' button to specify which admin users will receive notifications.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_67.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_31.png]]
 |}
+====Client Area Zones Status====
 {|
-|style="padding: 0px 0px 15px 15px;"|'''5. Custom Subnet IP Address''' - create zones and PTR records with an IP address included in a subnet related to the product. <br/>
+|style="padding: 10px 0px 20px 15px;"| Checking the selected boxes will result in an additional status concerning a given domain in the client area.
-'''''Note:''' This option works only if you have integrated your DNS Manager with [https://www.modulesgarden.com/products/whmcs/ip-manager IP Manager For WHMCS].''
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_68.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_31_1.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''5. rDNS Custom IP Address''' - create PTR records with a custom IP, enter a new IP address to create a new PTR.<br/> '''''Note:''' Both IPv4 and IPv6 are supported by DNS Manager For WHMCS.''
+|style="padding: 0px 0px 15px 15px;"| Pressing the ''Modify'' button next to a given option will cause a new window to appear where you can set up your own custom status by means of HTML.
+Your new description can include the ''{$domain}'' variable which will give the domain address back in the status message.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_68_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_31_2.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''6. Custom IP Address''' - create zones with a custom IP address, you have no IP addresses to choose from, you have to enter a new IP address.<br/> '''''Note:''' Both IPv4 and IPv6 are supported by DNS Manager For WHMCS.''
+|style="padding: 0px 0px 20px 15px;"| You can see an example status on the screen below.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_69.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS31_3.png]]
 |}
+===DNS Record Sets===
 {|
-|style="padding: 0px 0px 20px 15px;"|'''7. Client Area Record Sets''' - clients may manage DNS records sets.
+|style="padding: 10px 0px 20px 15px;"|Create ready made sets of DNS records. You will find them in '' 'Settings' → 'DNS Records Sets'. '' <br/>Press '' 'Add Set' '' to create a new one.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_69_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_23.png]]
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''8. Client Area Backups''' and '''Client Area Backups Limit''' - clients are given the option to create backups of their zones and upload backup files. <br/> It is advised to set a limit on the number of allowed backups. Default '' '-1' ''  indicates ''unlimited''
+|style="padding: 0px 0px 20px 15px;"|Enter the newly created set name.
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_69_2.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_24.png]]
 |}
 {|
-|style="padding: 0px 0px 10px 15px;"|'''9. Protect Zones On Product Termination''' - zones are not automatically deleted once the product has been terminated.
+|style="padding: 0px 0px 20px 15px;"|Once your new set appears on the list, you may edit that set in order to create records. Press '' 'Edit Record Set' '' to continue.
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|'''10. Show Product Name''' - a full product name is shown, instead of the general type with an order number.
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_24_1.png]]
+|}
+{|
+|style="padding: 0px 0px 20px 15px;"|List of records will appear. Please use the '' 'Add Record' '' button to continue.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_25.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|Now, fill out the data as required.<br/>
+'' '''Note:''' You may add adequate variables for domain and IP address and then these fields will be automatically changed to domain/zone IP when this record set is used.<br/>
+For example, if you have the '' 'example.com' '' domain with '' '123.123.123.123' '' IP address all you have to do is add the following variable to the DNS Record Set:''<br/>
+* '' '''{$domain}''' '' - will return full '' 'example.com' '' domain address
+* '' '''{$domainname}''' '' - will return only '' 'example' '' name
+* '' '''{$domainextension}''' '' -  will return '' 'com' '' extension
+*  '' '''{$ip}''' '' will return the '' '123.123.123.123' '' IP address; that can be:
+** IP address assigned to the domain by a client, provided while creating a zone
+** hosting dedicated IP address
+** WHMCS server address provided it is a hosting
+* '' '''{$serverhostname}''' '' - will return the DNS server address or its IP address, depending which one has been provided in the module's DNS server configuration in the admin area,<br/> e.g.: ''yourdnsserver.com'' or ''12.23.34.45''
+* '' '''{$ns1}''', '''{$ns2}''', '''{$ns3}''', '''{$ns4}''' '' and '' '''{$ns5}''' '' - will return the global nameservers addresses specified in the order basing on the sequential number of the corresponding data in the variables
+* ''{$serverassignedip'''X'''}'' – allows you to use '' 'Assigned IP Addresses' '' from another server configuration ('' WHMCS → System Settings → Servers''). <br/> '''Important!''' You need to replace '''X''' with a number. For example: If you provide {$serverassignedip'''1'''} in the DNS Record Set, '''the first''' address from the '' 'Assigned IP Addresses' '' section will be used.
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_25_1.png]]
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|Created DNS Records Sets can be then used while preparing ready packages, as it was described. <br/>Ready made sets allow much faster and more personal configuration of packages.<br/> There is also the possibility to duplicate the selected DNS Record Sets.
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS2_69_4.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_26.png]]
 |}
@@ Line 1,162: / Line 1,442: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS32_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_32_1.png]]
 |}
 {|
@@ Line 1,188: / Line 1,468: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS32_2.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_32_2.png]]
 |}
 {|
@@ Line 1,195: / Line 1,475: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS32_3.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_32_3.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|In practice, when a client will by trying to create a record using one of the forbidden words, the action will be blocked.
+|style="padding: 0px 0px 20px 15px;"|In practice, when a client will be trying to create a record using one of the forbidden words, the action will be blocked.
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS32_4.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_32_4.png]]
 |}
+===DNS Manager Logs===
+{|
+|style="padding: 10px 0px 20px 15px;"|This section helps you keep track of all the activities carried out in DNS Manager. Find them here: '' 'Settings' → 'Logs'. ''
+|}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_60.png]]
+|}
+===DNS Manager Tasks===
+{|
+|style="padding: 10px 0px 20px 15px;"|Check the list of current tasks. ''Keep in mind that tasks management is still in the DNS Manager V2 addon!''
+Use the cron tasks to delete '''all''' tasks with the '' 'Finished' '' status:
+ php -q /yourwhmcs/modules/addons/DNSManager3/cron/cron.php TasksCleaner --clean
+|}
+{|
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_60_1.png]]
+|}
+==DNS Manager V2 Addon==
+{|
+|style="padding: 10px 0px 30px 15px;"|To manage the following setting you will have to step back to the DNS Manager v2 addon module for a moment. You will find there the remaining section described below.
+|}
 ===Cron Jobs===
 {|
-|style="padding: 10px 0px 15px 15px;"|In order to manage your cron job tasks proceed to '' 'Tools' → 'Cron'. ''<br/>Here, you will find four information boxes, each one responsible for management of a separate cron task.<br/> These are: migration, import, synchronization and cleaner.
+|style="padding: 10px 0px 15px 15px;"|In order to manage your cron job tasks proceed to '' 'Tools' → 'Cron'. ''<br/>Here, you will find five information boxes, each one responsible for management of a separate cron task.<br/> These are: migration, import, synchronization, cleaner and backup.
 |}
 {|
@@ Line 1,247: / Line 1,549: @@
 *'''Inactive Services''' - with canceled, terminated and/or suspended status
 *'''Inactive Domains''' - with canceled and/or expired status
-PTR Records are removed:
+Decide for which of the following services, the PTR Records should be removed:
-*'''Inactive Services''' - if service is terminated or canceled
+*'''Terminated Services'''
+*'''Cancelled Services'''
+*'''Suspended Services'''
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''Cron Backup Scheduler'''
+In this section, you can schedule your backups. Similarly as previously, complete these fields according to your preferences.
+*'''Automatic Backup Limit''' - you can set a maximum number of backups that will be stored. If the provided number is exceeded, then the oldest backups will be overwritten.
 |}
 {|
@@ Line 1,346: / Line 1,655: @@
 |style="padding: 0px 0px 30px 15px;"|According to specifically set-up cron jobs all created tasks are regularly executed. Here, you can see the current status of each task.<br/> If it is queuing for the next cron run, is currently executed, aborted or complete. Check when they were executed for the last time ''(Last Execution)'' and when the task was added. <br/>Available actions: call execution manually and remove the task.
 |}
+<!--
+{|
+|style="padding: 10px 0px 20px 15px;"|DNS Manager v3 addon '' 'Tasks' '' section includes a list of tasks with their current status and allowed actions:
+*View task information details and logs
+*Download Task File ''(csv)''
+*Delete task
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_68.png]]
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_69.png]]
+|}
+{|
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS3_70.png]]
+|}
+-->
 ==Dashboard==
@@ Line 1,482: / Line 1,808: @@
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_55.2.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS3_55.2.png]]
-|}
-==DNS Manager Logs==
-{|
-|style="padding: 10px 0px 20px 15px;"|This section helps you keep track of all the activities carried out in DNS Manager. Find them here: '' 'Settings' → 'Logs'. ''
-|}
-{|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_60.png]]
 |}
@@ Line 1,532: / Line 1,850: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS_71_4.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_71_4.png]]
 |}
 {|
@@ Line 1,538: / Line 1,856: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_73.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_73.png]]
 |}
 {|
@@ Line 1,544: / Line 1,862: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_74.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_74.png]]
 |}
 {|
@@ Line 1,550: / Line 1,868: @@
 |}
 {|
-|style="padding: 0px 0px 20px 25px;"|[[File:DNS2_74_1.png]]
+|style="padding: 0px 0px 20px 25px;"|[[File:DNS4_74_1.png]]
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|You only need to remember that relevant options must be enabled in the '' 'General Settings' '' section.
+|style="padding: 0px 0px 20px 15px;"|You only need to remember that relevant options must be enabled in the '' 'Global Settings' '' section.
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_75.png]]
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_75.png]]
 |}
@@ Line 1,621: / Line 1,939: @@
 **'' 'userid -  ID of user
 **'' 'zone_ip' ''  - IP address assigned to the zone. If empty, a default IP address will be used
+**'' 'recordSet' '' - ID of the DNS Record Set, it can be downloaded from the base, table: ' ''dns_manager2_setrecord', '' field: '' 'setid' ''
 Exemplary use:
 <pre>
@@ Line 1,631: / Line 1,950: @@
   'zone_ip' => '192.168.56.101',
   'userid' => '1',
+ 'recordSet' => '2',
 );
 </pre>
@@ Line 1,668: / Line 1,988: @@
 </pre>
 *'' 'getZone' '' -  returns the zone with records. Use with these parameters:
-***'' action = dnsmanager' ''
+***'' 'action = dnsmanager' ''
-***'' dnsaction = getZone' '' - DNS action that DNS Manager should execute
+***'' 'dnsaction = getZone' '' - DNS action that DNS Manager should execute
-***'' zone_id' '' - ID of the zone that should be retrieved (use ID from WHMCS)
+***'' 'zone_id' '' - ID of the zone that should be retrieved (use ID from the dns_manager2_zone table)
+***'' 'zone_name' '' - name of the zone
 *'' 'removeZone' '' -  deletes the zone. Use with these parameters:
@@ Line 1,687: / Line 2,008: @@
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|3. 255 characters in ''TXT'' records is a maximum limit for the '' 'PowerDNS' '' submodule.
+|style="padding: 0px 0px 20px 15px;"|3. 255 characters in ''TXT'' records is a maximum limit for the '' 'PowerDNS' '' and '' 'cPanel' '' submodules.
 |}
+<!--
 {|
 |style="padding: 0px 0px 20px 15px;"|4. When you try to add a record of not supported type to a package, you will be informed about the lack of support with a note as on the screen below.
@@ Line 1,694: / Line 2,016: @@
 {|
 |style="padding: 0px 0px 20px 25px;"|[[File:DNS_x1.png]]
+|}-->
+{|
+|style="padding: 0px 0px 20px 15px;"|4. As this module supports templates system, any changes made in the module's templates files will be saved after the upgrade process.
 |}
 {|
-|style="padding: 0px 0px 20px 15px;"|5. As this module supports templates system, any changes made in the module's templates files will be saved after the upgrade process.
+|style="padding: 0px 0px 15px 15px;"|5. In case you are using cPanel or cPanel Extended provisioning modules with DNS Manager, it is '''highly''' advised to enable the '''Existing Zone Update''' option.<br/> Otherwise, DNS zone will be previously created by the provisioning module, not by DNS Manager where an error notification on already existing zone will appear. That will cause such zone will not be visible on the Zones List. <br/> If the mentioned option is enabled, DNS Manager will fail to check whether the zone already exists and consequently the created by the provisioning module entry will be added to the Zones List.
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|6. In case you are using cPanel or cPanel Extended provisioning modules with DNS Manager, it is '''highly''' advised to enable the '''Allow Update Of Existing Zone''' option.<br/> Otherwise, DNS zone will be previously created by the provisioning module, not by DNS Manager where an error notification on already existing zone will appear. That will cause such zone will not be visible on the Zones List. <br/> If the mentioned option is enabled, DNS Manager will fail to check whether the zone already exists and consequently the created by the provisioning module entry will be added to the Zones List.
+|style="padding: 0px 0px 30px 25px;"|[[File:DNS4_77.png]]
 |}
 {|
-|style="padding: 0px 0px 30px 25px;"|[[File:DNS_77.png]]
+|style="padding: 0px 0px 15px 15px;"|6. Please note that from the 2.13.0 version of the module, it is '''obligatory''' to use a dot at the end of each domain while adding or editing '' 'DNS Records' '' and '' 'DNS Record Sets' ''.<br/> If you do not provide a dot, the module will double your domain. Take a look at the following examples, on the left side we present what is typed by a client and on the right side you can see the module’s interpretation:<br/>
+An exemplary zone name is '''example.com'''<br/>
+@ → example.com. <br/>
+example.com → example.com.example.com. <br/>
+example.com. → example.com. <br/>
+www.example.com. → www.example.com. <br/>
+www.example.com  → www.example.com.example.com. <br/>
+www → www.example.com. <br/>
+www. → www.example.com. <br/>
+www.@ → www.example.com. <br/>
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|7. Now you may use '' 'API Token' '' instead of '' 'API Key' '' to configure the Cloudflare submodule. Before you generate your '' 'API Token' '' in your Cloudflare panel, please remember to set the following '''read/edit''' permissions there:
+*User/User Details – Read
+*Zone/Zone – Edit
+*Zone/Zone Settings - Edit
+*Zone/DNS - Edit
+|}
+{|
+|style="padding: 0px 0px 15px 15px;"|'''8. How to correctly add translations of the DNS server errors into the language file:'''<br/>
+Most errors include a string with a domain name, to add a custom error message, you have to replace this string with ''':domain_word:''' phrase. <br/>
+An example of currently displayed error message:
+  RRset A.testdnsipdefault.by. IN CNAME: Conflicts with pre-existing non-CNAME RRset
+In this case '''A.testdnsipdefault.by.''' must be replaced with ''':domain_word:'''<br/>
+A correctly generated lang snippet will look as follows:
+  $_LANG['addonCA']['dashboard']['errors']['RRset :domain_word: IN CNAME: Conflicts with pre-existing non-CNAME RRset'] = "Some serious problem occurred with :domain_word:";
+As a result the below message will be displayed in the module:
+  Some serious problem occurred with A.testdnsipdefault.by.
+Of course, you may skip the domain name in the final output or add a fully customized error message:
+  $_LANG['addonCA']['dashboard']['errors']['RRset :domain_word: IN CNAME: Conflicts with pre-existing non-CNAME RRset'] = "Some serious problem occurred";
+  $_LANG['addonCA']['dashboard']['errors']['RRset :domain_word: IN CNAME: Conflicts with pre-existing non-CNAME RRset'] = 'My custom translation';
+If you do not add any translation in to the lang file, an original error message will be displayed.
 |}
 <!--
@@ Line 1,740: / Line 2,101: @@
 =Update Instructions=
 {|
-|style="padding: 10px 0px 30px 15px;"|The essential guidance through the process of updating the module is offered '''[https://www.docs.modulesgarden.com/How_To_Update_WHMCS_Module here]'''.<br/><br/>
+|style="padding: 10px 0px 30px 15px;"|The essential guidance through the process of updating the module is offered '''[https://www.docs.modulesgarden.com/How_To_Update_WHMCS_Module here]'''.<br/>
-Keep in mind there is a quick and easy option in our client area that will let you upgrade the license of your module to an open source version at any time - and at a lower price!<br/>
+Ensure successful completion of the module update by carefully following each step, thereby preventing data loss or any unforeseen issues.<br/> Additionally, you will find a current list of supplementary actions necessary for a smooth update process there.
-To take advantage of it, simply use the '''License Upgrade''' button located on the product's page and a discounted invoice will be generated automatically.<br/>
 |}
-==Migration==
+==Migration from V2x.x to V3.x.x==
+{|
+|style="padding: 10px 0px 30px 15px;"|If you want to migrate your DNS Manager For WHMCS to version 3.0, please follow the below steps:
+*Keep both module addons '''DNS Manager''' and '''DNS Manager v3''' active
+*Full module configuration is still located in DNS Manager addon module, your old data are not lost
+*Move to DNS Manager '''v3''' addon module → '' 'Settings' '' to enable access to Client Area with support for '' 'Twenty-One' '' theme
+**Set up a new cron task ''(DNS Manager '''v3''' addon module → Settings)''
+*Go back to ''DNS Manager addon module'' → 'Settings' → 'Global Settings' → 'Client Area Zones Status' '' and again save the content. <br/> '''''Note:''' Entered content might not be correctly displayed in the new client area view, saving the changes will ensure there are no unexpected errors or missing information.''
+|}
+==Migration of Zones==
 {|
 |style="padding: 10px 0px 15px 15px;"|'' 'Migration' '' is another useful tool that you may use to manage zones efficiently. With this tool you may migrate zones between servers. <br/>
-Keep in mind, that when you are migrating zones from one server to another they are not imported to your WHMCS in the meantime!<br/> If you wish to update the list of migrated zones, you will have to import them to WHMCS from the final server after migration.<br/>
+Keep in mind, that if you wish to transfer the relation that exists in the DNS Manager module to the target server, you must select the '' 'Move Management To Target Server' '' option.<br/> Otherwise, only the zone will be copied from the original to the target server, the relation to the original server will remain in the module.<br/>
 <br/>
 Remember that migrated zones are available on both servers now! Migration does not delete zones, just copy them to the new server!
@@ Line 1,756: / Line 2,126: @@
 {|
 |style="padding: 0px 0px 15px 15px;"|To add a migration task, press '' 'Add Migration', '' specify from which server you wish to migrate zones, and the target server, as simple as that.<br/>
-'''''Note:''' Migration does not copy DNS Manager settings, to illustrate: if you are migrating zones that exist in DNS Manager their locations for example are not updated.''
+'''''Note 1:''' Migration does not copy DNS Manager settings, to illustrate: if you are migrating zones that exist in DNS Manager their locations for example are not updated.'' <br/>
+'''''Note 2:''' You can decide if the option of managing zones should be transferred to the target server. To do it, please tick 'Move Management To Target Server' .
 |}
 {|
@@ Line 1,778: / Line 2,149: @@
 {|
 |style="padding: 0px 0px 30px 25px;"|[[File:DNS_41_3.png]]
+|}
+=Upgrade Guide=
+{|
+|style="padding: 10px 0px 30px 15px;"|Seeking a solution that offers greater flexibility, customization tailored to your precise needs, and unrestricted availability?<br/> There is an option that not only proves to be cost-effective in the long run but also includes prioritized support services, making it a truly valuable investment.<br/>
+Opt for the [https://www.modulesgarden.com/products/whmcs/dns-manager#open-source-version Open Source version] of your DNS Manager For WHMCS module to unlock these benefits.<br/> Simply click on either the '''Get Source Code''' or '''Upgrade To Lifetime''' button found on the product's page in our client area to complete the one-step upgrade process, with a '''dedicated discount''' already applied.<br/>
+Follow a [https://www.docs.modulesgarden.com/How_To_Upgrade_WHMCS_Module comprehensive guide] covering the transition process, the advantages it brings, and step-by-step instructions on what to do next after the order has been successfully finalized.
 |}
@@ Line 1,792: / Line 2,171: @@
 |}
 {|
-|style="padding: 0px 0px 10px 25px;"|[[File:DNS8_1.png]]
+|style="padding: 0px 0px 10px 25px;"|[[File:DNS4_81.png]]
 |}
 {|
@@ Line 1,799: / Line 2,178: @@
 |}
 {|
-|style="padding: 0px 0px 30px 15px;"|5. In case your backup task started in your client area is not being processed, make sure that your Cron Import job is not disabled or set to a low frequency.
+|style="padding: 0px 0px 10px 15px;"|5. In case your backup task started in your client area is not being processed, make sure that your Cron Import job is not disabled or set to a low frequency.
 |}
+{|
+|style="padding: 0px 0px 5px 15px;"|6. Error: "The selected zone is already taken"<br/>
+''Reason 1:'' A zone with the same name already exists in dns_manager2_zone table (you can also find it on the '' 'Zones List' '' in the addon)<br/>
+''Reason 2:'' Other client is using such domain with a product or has it registered. It is allowed as long as the other client's domain status is: ''Cancelled, Transferred Away, Fraud'' or ''Terminated'' <br/>
+'''Solution:''' Find the domain in WHMCS and cancel it <br/>
+''Reason 3:'' Zone already exists on the DNS server (e.g. cPanel)
+|}
+{|
+|style="padding: 0px 0px 30px 15px;"|7. Error: "Message: API failure: (XID 2ugbb6) You do not have access to a domain named “domain.tld”."<br/>
+If you encounter the above error for a zone associated with a cPanel server, it means that you need to set '''root user permissions''' for the token that is used in the cPanel submodule configuration.
+|}
+<!--{|
+|style="padding: 0px 0px 30px 15px;"|7. In case you have encountered issues with setting up an invalid zone type with the '''"Allow Update Of Existing Zone"''' option enabled,<br/> please use the '''"linkedZonesFixer"''' argument in the cron command to overcome the problems that have arisen.
+|}-->
 <!--
   If after successful installation in your client area you receive the following or similar error:
@@ Line 1,852: / Line 2,246: @@
 |}
 -->
+Seeking a solution that offers greater flexibility, customization tailored to your precise needs, and unrestricted availability?<br />
+There is an option that not only offers cost-effective, long-term maintenance but also includes prioritized support services, making it a truly valuable investment.<br />
+Opt for the [http://www.docs.modulesgarden.com/index.php?title=DNS_Manager_For_WHMCS&oldid=19472 Open Source version] of your DNS Manager For WHMCS module and unlock these benefits.<br />
+Simply use either the '''Get Source Code''' or '''Upgrade To Lifetime''' button found on the product's page in our client area, and proceed with our one-step upgrade order with a '''dedicated discount''' already applied.<br />
+Follow a [http://www.docs.modulesgarden.com/index.php?title=DNS_Manager_For_WHMCS&oldid=19472 comprehensive guide] covering the transition process, the advantages it brings, and step-by-step instructions on what to do next after the order has been successfully completed.<br />

Personal tools

Namespaces

Variants

Views

Actions

Search

DNS Manager For WHMCS

Latest revision as of 12:51, 19 April 2024

DNS Manager V3 For WHMCS requires an active DNS Manager For WHMCS. You must keep both addons active to be able to use the newest version of DNS Manager module in full.

Contents

[edit] About DNS Manager V3 For WHMCS

[edit] Installation

[edit] Configuration and Management

[edit] Basic Configuration

[edit] Servers Configuration

[edit] BIND 9 Configuration

[edit] Management of Packages

[edit] Items

[edit] Servers

[edit] Records

[edit] Notifications

[edit] Registrars

[edit] IP Management

[edit] Client Area

[edit] DNS Management in Client Area

[edit] Zones

[edit] DNSSEC

[edit] Bulk Management

[edit] rDNS

[edit] Record Sets

[edit] Backups

[edit] Tasks

[edit] Zones Management

[edit] Additional Tools

[edit] Settings

[edit] Global Settings

[edit] Templates

[edit] Logs And Notifications

[edit] Slave Zones

[edit] Other

[edit] Notifications

[edit] Client Area Zones Status

[edit] DNS Record Sets

[edit] DNS Blocked Strings

[edit] DNS Manager Logs

[edit] DNS Manager Tasks

[edit] DNS Manager V2 Addon

[edit] Cron Jobs

[edit] Import

[edit] Zone Backups

[edit] Tasks

[edit] Dashboard

[edit] Custom cPanel Zone Templates

[edit] IP Manager For WHMCS Integration

[edit] DNS Manager Migrator

[edit] API Methods

[edit] Tips

[edit] Update Instructions

[edit] Migration from V2x.x to V3.x.x

[edit] Migration of Zones

[edit] Upgrade Guide

[edit] Common Problems

Navigation

WHMCS Modules

WHMCS Widgets

Translations

cPanel Modules

General

FAQ

Community

DNS Manager For WHMCS

DNS Manager V3 For WHMCS requires an active DNS Manager For WHMCS.
You must keep both addons active to be able to use the newest version of DNS Manager module in full.