flamegrill
Verified User
Hi there,
Currently da checks the named.conf file to decide weather or not a domain is on the system already or not.
I think this check is no where near complete enough. I believe a central file in /usr/local/directadmin/data/admin/ would be better suited.
Reasons:
1) We for 1 don't use DA for dns as we developed a central management system years ago and we also use Helm and cPanel.
2) During server migrations in the above scenario we ignore named.conf and the zone files simply because they are not needed, infact we typically don't have named enabled.
3) it would be handy to have a list of all domains readily available that is easily accessible for many many different applications.
Thanks
Paul
Currently da checks the named.conf file to decide weather or not a domain is on the system already or not.
I think this check is no where near complete enough. I believe a central file in /usr/local/directadmin/data/admin/ would be better suited.
Reasons:
1) We for 1 don't use DA for dns as we developed a central management system years ago and we also use Helm and cPanel.
2) During server migrations in the above scenario we ignore named.conf and the zone files simply because they are not needed, infact we typically don't have named enabled.
3) it would be handy to have a list of all domains readily available that is easily accessible for many many different applications.
Thanks
Paul