Skip to end of metadata
Go to start of metadata

With the Reverse DNS Management Plugin, which we deliver for free with the module, you can add reverse DNS servers and admins and customers can manage the reverse DNS record of IPs. The plugin is fully AJAX driven.

Supported providers:

  • PowerDNS

We decided to add PowerDNS as the first provider because PowerDNS is very common and is also used by SolusVM and Virtualizor. So the existing name servers can be added to the module. However, the Reverse DNS Plugin is flexible and expandable. Anyone with knowledge of PHP can add their own providers, so you can expand the number of supported providers yourself. For example, it is possible to integrate the data center API for RDNS management.

For maximum flexibility, multiple RDNS servers can be added and different subnets can be assigned to each RDNS server.

 

Explanation of the overview table

ColumnFunction
IDInternal server id
ServernameThe friendly name of the server for easier identification
TypeProvider type
StatusResult of the connection test
AssignmentsList of assigned subnets




 

Explanation of the setup steps

The installation of a name server server is not described here. If you are not sure about this, please contact the support.

Add RDNS Server

The first step is to add an RDNS server. After you have selected the provider, the configurable fields will be displayed, which you have to fill in accordingly.

Add Assignment

The next step is to assign subnets to the RDNS server. Using the button "Add Assignment" in the "Action" column, allows you to create assignments. Please note that you must create for each /24 subnet an own assignment. The IP must end with "0".

If you are using PowerDNS and the subnet has not yet been created on the name server, you must first create an appropriate DNS zone for the subnet. This can be done with the button "Create Zone".

Testing the functionality

If you have added the server correctly and the status indicator is green, you can try setting an RDNS entry via the IP Manager. If the function does not work, please check the WHMCS debug log.

To allow customers to set RDNS entries, you need to enable the feature in the ACL group. The customer is only offered to set RDNS entries if the subnet is assigned to a nameserver. Without assignment, or without ACL permission, no option to edit the RDNS will appear.







  • No labels