When creating a new DNS zone using the wizard is it possible to have the template specify the mail server for a record? Here is my current template record. There is a variable {IP} that is my website and it correctly gets picked up. Is there a way to specify something other then {IP} like maybe {MAILIP} or some other variable to have it autofill the correct value for mail A record? Right now I have to manually fix the mail A record for each domain, but there has to be a way for it to pick up my mail server IP in a multiserver setup. Thanks! origin={DOMAIN}. ns={NS1}. ns={NS2}. mbox={EMAIL}. refresh=7200 retry=540 expire=604800 minimum=86400 ttl=3600 [DNS_RECORDS] A|{DOMAIN}.|{IP}|0|3600 A|www|{IP}|0|3600 A|mail|{IP}|0|3600 NS|{DOMAIN}.|{NS1}.|0|3600 NS|{DOMAIN}.|{NS2}.|0|3600 MX|{DOMAIN}.|mail.{DOMAIN}.|10|3600 [ZONE] origin={DOMAIN}. ns={NS1}. ns={NS2}. mbox={EMAIL}. refresh=7200 retry=540 expire=604800 minimum=86400 ttl=3600 [DNS_RECORDS] A|{DOMAIN}.|{IP}|0|3600 A|www|{IP}|0|3600 A|mail|{IP}|0|3600 NS|{DOMAIN}.|{NS1}.|0|3600 NS|{DOMAIN}.|{NS2}.|0|3600 MX|{DOMAIN}.|mail.{DOMAIN}.|10|3600
If you have just one mailserver in your cluster, then replace {IP} with the IP address of the mailserver inside the template.
Sounds good for now. But what happens when I add a second mail server. Would be good if somehow the DNS Wizard reads the clients template and is able to extract maybe {MAILIP] and {DBIP} from clients template and use them in DNS templates. Keep the {IP} just for the website. Thanks!
webguyz, I've been looking into the same as you and have decided to create multiple templates, one for each web server/mail server combination. At least until we get the option to specify custom fields in the template/wizard. If you add another mail server, replace the current template and add new domains to the new mail server. As great as ISPConfig seems, there are a lot of weak spots for the inexperienced admin. For instance nothing's stopping you from assigning one mail server in DNS and another in the mail config. The lack of fail safes in the design can bite anyone in the ass, especially if you have a NAT setup and have to juggle both private and public IP addresses. PS! Also in your template, the NS is specified twice in the [zone]. This won't work, as the second instance will overwrite the first.
