You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found out the "clone of" feature very useful, but I wish to bring it to an higher level.
The idea is quite simple: it's to be able to link a DNS master zone to a single template.
The zone will first inherits all records from the template.
The zone will then removes the records that has a "negative" override. (say "don't inherit")
The zone will then override all the records that are defined both within itself and within the template.
The zone will then have the additionnal records that are only defined within itself
Of course, when we edit a template, all the zones that links to that template will get updated, using the previous rules.
Like that, we will be able to directly represent our needs, where 95% of the zones are the exactly the same, and the other 5% has only little difference, such as a different MX records.
Thanks
The text was updated successfully, but these errors were encountered:
This is a good suggestion and should be doable. I have a similar idea for fmFirewall so I will probably code this feature into both modules at the same time.
This request is fulfilled in the upcoming release except for your request to override records that exist in the template and cloned zone. Because multiple records for the same record name can exist and are valid, it's best to have the user skip the unwanted records.
I found out the "clone of" feature very useful, but I wish to bring it to an higher level.
The idea is quite simple: it's to be able to link a DNS master zone to a single template.
The zone will first inherits all records from the template.
The zone will then removes the records that has a "negative" override. (say "don't inherit")
The zone will then override all the records that are defined both within itself and within the template.
The zone will then have the additionnal records that are only defined within itself
Of course, when we edit a template, all the zones that links to that template will get updated, using the previous rules.
Like that, we will be able to directly represent our needs, where 95% of the zones are the exactly the same, and the other 5% has only little difference, such as a different MX records.
Thanks
The text was updated successfully, but these errors were encountered: