Default DNS Template

XN-Matt

The new feature to change the default DNS template is good although a bit short of the mark.

We really need to be able to edit the default template used to create a new zone. There are a number of things we need to change (removal of pop/smtp records), changing the default SPF record but without an %ip variable (ideally %mail-ip and %web-ip to map to respective services), we cannot do that.

We also want our TTLs on records to be lower by default too.

Please can you consider adding this function within the same section to see the existing/default template and change as required.

mendozal

XN-Matt +1 from me, for the flexibility.

Adam

We do plan to add customisation for the default TTL and SOA.

The current DNS template functionality should allow you to customise your SPF whilst retaining the allows for your Enhance cluster. If you haven't changed the MX you can just retain the "mx" selector within the record to capture the IP of the assigned mail server. If you have changed the MX (perhaps to a mail filtering gateway) you could use use mail.$$origin$$ instead. There is generally no need to allow the website IP but you could by retaining the "a" selector.

Oldschool

Adam
Is there a list of the variables like $$origin$$ or is that the only variable?

xtego

Oldschool I second this question. Is there ability to use ip variables in dns templating? Or is this planned? This would be very helpful.

Adam

$$origin$$ is the only variable. You shouldn't need IP variables because you can use a CNAME instead.

adil

Will there be an update on this feature ?

So we can have DNS template per Package.

GustavoM

How can I edit all default TTLs? The current setting of 1 day is not ideal because if you need to move sites between servers, DNS propagation could keep them offline for up to 24 hours.

I'd like to change all TTLs to 1 hour.

It would be helpful if the platform's default template were listed on the "DNS zone templating" screen, so we could edit the necessary records and add what we need.

As a suggestion, it would be very useful to have "DNS zone templates" tied to specific plans, as each plan might have different needs, such as an external MX outside the Enhance platform. This would eliminate the need for manual editing.