Ok, i decided it was cheeper to buy a wildcard certificate for my servers instead of a certificate per server. Although there is nothing documentated about this situation i decided i'll give it a try 
I managed to install the certificates for both directadmin as apache on multiple servers this way:
-Create a certificate request on server A. SAVE THE KEY AND CSR!!!!
(use *.domain.com as Common name)
-Go and get your wildcard certificate using the crt
now you got your certificate (*.crt) and the key you have saved.
i use server.crt and server.key
-you can paste the crt and key as normal in server A to accomplish the request for server A.
-now login on server B using sftp of scp as root
-find /etc/httpd/conf/ssl.crt/blabla.crt and replace it with your server.crt (ALWAYS MAKE A BACKUP OF THE EXISTING FILES!!!!)
-find /etc/httpd/conf/ssl.key/blabla.key and replace it with your server.key (ALWAYS MAKE A BACKUP OF THE EXISTING FILES!!!!)
-find /usr/local/directadmin/conf/directadmin.conf and edit the following lines:
SSL=0
replace with
SSL=1
apachecert=/etc/httpd/conf/ssl.crt/server.crt <-- change to your path
apachekey=/etc/httpd/conf/ssl.key/server.key <-- change to your path
cacert=/etc/httpd/conf/ssl.crt/server.crt <-- change to your path
cakey=/etc/httpd/conf/ssl.key/server.key <-- change to your path
save & exit
from a ssh terminal:
service httpd restart
service directadmin restart
Now verify both apache (https://www.domain.com) and directadmin (https://www.domain.com:2222) can be accessed without a security warning.
So that's a way to set up wildcard certificates on multiple servers.
now i got a question for you guys
if you login on server B and go to user level-->SSL certificates
it still says "use the server shared certificate" although if you browse to https://serverB.domain.com and view the certificate it reports as the valid wildcard certificate.
Anyone knows what can be the cons??
I managed to install the certificates for both directadmin as apache on multiple servers this way:
-Create a certificate request on server A. SAVE THE KEY AND CSR!!!!
(use *.domain.com as Common name)
-Go and get your wildcard certificate using the crt
now you got your certificate (*.crt) and the key you have saved.
i use server.crt and server.key
-you can paste the crt and key as normal in server A to accomplish the request for server A.
-now login on server B using sftp of scp as root
-find /etc/httpd/conf/ssl.crt/blabla.crt and replace it with your server.crt (ALWAYS MAKE A BACKUP OF THE EXISTING FILES!!!!)
-find /etc/httpd/conf/ssl.key/blabla.key and replace it with your server.key (ALWAYS MAKE A BACKUP OF THE EXISTING FILES!!!!)
-find /usr/local/directadmin/conf/directadmin.conf and edit the following lines:
SSL=0
replace with
SSL=1
apachecert=/etc/httpd/conf/ssl.crt/server.crt <-- change to your path
apachekey=/etc/httpd/conf/ssl.key/server.key <-- change to your path
cacert=/etc/httpd/conf/ssl.crt/server.crt <-- change to your path
cakey=/etc/httpd/conf/ssl.key/server.key <-- change to your path
save & exit
from a ssh terminal:
service httpd restart
service directadmin restart
Now verify both apache (https://www.domain.com) and directadmin (https://www.domain.com:2222) can be accessed without a security warning.
So that's a way to set up wildcard certificates on multiple servers.
now i got a question for you guys
if you login on server B and go to user level-->SSL certificates
it still says "use the server shared certificate" although if you browse to https://serverB.domain.com and view the certificate it reports as the valid wildcard certificate.
Anyone knows what can be the cons??