DNS Manager and templates

[Remitur]

A question about templates: is it possible anyway to apply to the same zone different DNS record sets?

Let's show how and why:

- A certain domain is registered; has is own zone, created using a parking template

- customer buys an hosting service; I would like to apply to the DNS zone (still existing) another template (which create 2-3 A records to manage the hosting service)

- customer buys an email service: I would like to apply a third template, wwith (i.e.) MX and SPF records.

But as I try to do it, I get an error (zone still existing), and can't do it...

Any way to do it?

Beside this, some suggestions:

- made the function "import zone from file" and "export zone to file" available in client area too: it's a great way to let customers doing a backup of their own zones on their own

- made the "DNSrecord set" template available in client area: so a customer can apply a certain DNS templates on his own (example: I made a template for using Google mail services: a customer apply it, and with a single click he find all the DNS record needed ready... or a customer can create his own template, and apply it on each of his own domains)

[Joanna]

First and foremost, thank you for these constructive suggestions, your valuable insight is greatly appreciated!

With regard to your query concerning the templates, it is not possible to follow a described scenario in the current version of our module, unfortunately. Nevertheless, this functionality has been added to the list of concepts worth giving further consideration and as such it may appear in the future releases of DNS Manager For WHMCS.

[Remitur]

Maybe it would be quite easy to do it (= add record as needed when a service is activated) trough a hook and some coding...

It seems that an internal API exists ( https://www.docs.modulesgarden.com/DNS_ ... WHMCS#Tips ) but docs about it is obscure.

i.e.:

'clientid' - id of a client, record will be assigned to that client

That's to say that I might have different records belonging to same zone, but assigned to different clients?!?!?!
A zone is assigned to a client, and every record in that zone is assigned to the same client too...
Or does it mean something totally different from what I understood?

'removeRDNS' - allows removing existing rDNS record. Additional, required parameters:
'serverid' - ID of a server
'ip' - IP address that will be used

Right, but... how can I specify the record to be removed?
And... if I remove a record, why is needed to specify "IP address that will be used" ? For what will be used that IP?



Would it be possible to get some sample code? (more specific and useful that the generic sample code provided in your kb)

Or - last question - those API are available only for reverseDNS, and does not exist any API to set, manage or delete other DNS records?!

[Joanna]

That's to say that I might have different records belonging to same zone, but assigned to different clients?!?!?!
A zone is assigned to a client, and every record in that zone is assigned to the same client too...
Or does it mean something totally different from what I understood?

It is important to understand that rDNS are considered to be separate zones and thus the ID of a client is required to assign a zone to them.

Right, but... how can I specify the record to be removed?
And... if I remove a record, why is needed to specify "IP address that will be used" ? For what will be used that IP?

You indicate the record to be removed by providing the IP address that has been specified upon its addition.

Would it be possible to get some sample code? (more specific and useful that the generic sample code provided in your kb)

That should not be a problem, feel free to put in such a request to our specialists from the Support Team.

Or - last question - those API are available only for reverseDNS, and does not exist any API to set, manage or delete other DNS records?!

DNS Manager For WHMCS does not provide any other API options for the time being. Reverse DNS options have been implemented at the request of our customer. You are no less welcome to suggest other options and we will try our best to incorporate them into the module.

[Remitur]

I've found that somethink like what I proposed (the DNS set/template available in user area) is still available ... but I discoverd it only reading a little note in changelog, not from wiki documentation ...

Two notes:

* Amongst "features" ( https://www.modulesgarden.com/products/ ... ns-manager ) it's witten that it's possible "Restore Zone From DNS Records Set" in client area
But... how? It seems that it's possible only to delete a zone, and then recreating it applying a certain record set... but this is different from "restore zone"

* it would be great if, in client area, would be possible to apply DNS record set freely, in any moment, and not only when a zone is created

[Joanna]

Thank you most warmly for yet another dose of invaluable thoughts!

* Amongst "features" ( https://www.modulesgarden.com/products/ ... ns-manager ) it's witten that it's possible "Restore Zone From DNS Records Set" in client area
But... how? It seems that it's possible only to delete a zone, and then recreating it applying a certain record set... but this is different from "restore zone"

We deeply appreciate your bringing this matter to our attention. A slight error crept into the wording of the feature in question, and, regrettably, altered its meaning. Your clients are free to create zones using both ready-made and individually formulated sets of DNS records. Using the sets to restore a zone is currently not possible but we will try our best to incorporate such a component upon the future module's updates.

* it would be great if, in client area, would be possible to apply DNS record set freely, in any moment, and not only when a zone is created

This idea has been added to our to-do list and will be put into practice once deemed viable. You are more than welcome to put in other suggestions concerning the management of DNS records sets. Each of them will be given careful consideration and scheduled for implementation within further development of DNS Manager For WHMCS.