Description
About alternc-slavedns
When you install an alternc instance, your are prompted to configure two NS servers, DNS1 and DNS2. These are not DNS resolvers of your local networks, but the NS servers of the zones you will configure in your AlternC panel, those that you have to provide to the registrar when you register a DNS zone. These NS servers must obviously be configured by AlternC, and these is done either because the NS server is the AlternC server itself (its bind daemon, more specifically) either because they run an alternc-slavedns which synchronizes a bind DNS server with slave zones with their master in the AlternC main server, for the list of zones that are shared through a webpage.
Work proposed for this repo
We want to extend the AlternC main role to allow the configuration of alternc-slave DNS accounts (Administrator panel -> Slave DNS accounts), and a role to install and configure alternc-slavedns in a host.
The set of variables must be coherent (an account being the same object for client and server) and addressable as group variables.
Technique's issue
The AlternC role adresses AlternC configuration setting data directly to the database, with SQL sentences. This technique is not very sustainable, as the database structure is not an API, and leads to idempotency problems.
It would be better to use AlternC API, which is mentioned but not consistently documented somewhere, just a few mentions int he code. We can start trying for alternc-slavdns role, and only then eventually refactor alternc main role.