Automatically create DNS on site creation

[pmcun]

I've got a question regarding a feature I find very nice in ISPConfig 2, but that I can't find yet in the beta of ISPConfig 3 (correct me if I'm wrong ...).

When you create a site, in ISPConfig 2 it automatically created the DNS (if you checked the boxes to do so). I can't find those checkboxes in ISPConfig 3. Would love to see it implemented, thanks!

[ahagadorn]

I am just getting started with the Beta version, and I see a lot of potential. I am a VHCS2 user at the moment.

Auto DNS creation is one of the first things I thought of too, and I was going to dive in and code it. Is anyone else already working on this feature?

Andy

[till]

My idea for ISPConfig 3 is to implement it not as a checkbox in the website settings as all modules should be able to work independantly. Instead of that, my idea is to add some kind of whizard to setup new domains. E.g. the whizard asks just for the domain name, the client, the webspace size and IP and then creates the website in the sites module, the dns records in the dns module and the mail domain in the mail module. The whizard should be template driven, so that you can select a template for what the whizard shall do exactly, e.g. which DNS records shall be added. An example for such a template might be:

Example (simplified): Create only website and mail:

[site]
SITE|192.168.0.100|{domain}
ALIAS|www.{domain}|{domain}

[mail]
DOMAIN|{domain}
MAILBOX|webmaster@{domain}|10M

[dns]

or a template that creates also the dns records:

[site]
SITE|192.168.0.100|{domain}
ALIAS|www.{domain}|{domain}

[mail]
DOMAIN|{domain}
MAILBOX|webmaster@{domain}|10M

[dns]
SOA|{domain}
A|{domain}|192.168.0.100
A|www.{domain}|192.168.0.100

I started already to work on that. Vlaues in {} will be replaced by the values entered in the whizard.

[quentusrex]

I would be willing to help with this feature. I think it would also be helpful to users to have a template that would automatically create e-mail forwarding addresses for standard e-mail accounts. Like, if the user wants the e-mail account of 'Joe@mydomain.com', then have a template that creates a forward for 'admin@mydomain.com' and any other addresses. This is different from a catch-all because you can have two real accounts, and have the tech accounts like 'admin' and 'support' forward to one person, and the 'accounting' and 'sales' forward to another.