I appear to be having a couple of issues with my ISPconfig and letsencrypt configuration. The question 1st I have is, can I create a subdomain in ISPconfig such as test.example.com and only have a cname dns record for * to example.com and an A record for example.com to my ip address. Will this be sufficient validation for letencrypt or do I need an A record for each subdomain I want to use? I tried setting up my own dns server but turns out my isp is blocking port 53 so had to bail on that idea. The 2nd question or problem is a little more complicated, I best explain my setup first. I have 3 domains registered. matthewobrn.com meldp.com meldp.com.au all of them have dns records as follows: Code: meldp.com. A 3600 22.214.171.124 * CNAME 3600 meldp.com. meldp.com. MX 3600 mail.meldp.com. 10 meldp.com. NS 3600 ns1.netregistry.net. meldp.com. NS 3600 ns2.netregistry.net. meldp.com. NS 3600 ns3.netregistry.net. When I create a website in ISPconfig for matthewobrn.com with a ssl cert from letsencrypt it works. Then I create a site for meldp.com also with a ssl cert from letsencrypt and when I try to view the page is serves the ssl cert for matthewobrn.com The same for meldp.com.au. If I create a subdomain as a website such as test.matthewobrn.com letsencrypt fails. Here is the letsencrypt log for test.matthewobrn.com: Code: 2016-08-27 03:49:14,521:DEBUG:certbot.main:Root logging level set at 30 2016-08-27 03:49:14,525:INFO:certbot.main:Saving debug log to /var/log/letsencrypt/letsencrypt.log 2016-08-27 03:49:14,528:WARNING:certbot.cli:You are running with an old copy of letsencrypt-auto that does not receive updates, and is less reliable than more recent versions. We recommend upgrading to the latest certbot-auto script, or using native OS packages. 2016-08-27 03:49:14,529:DEBUG:certbot.main:certbot version: 0.8.1 2016-08-27 03:49:14,529:DEBUG:certbot.main:Arguments: ['-n', '--text', '--agree-tos', '--expand', '--authenticator', 'webroot', '--server', 'https://acme-v01.api.letsencrypt.org/directory', '--rsa-key-size', '4096', '--email', [email protected] I followed the perfect server setup for Debian Jessie and ISPConfig 3.1. Thanks for any help.