Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command:sudo certbot certonly -d *.alancameron.net
It produced this output: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. You may need to use an authenticator plugin that can do challenges over DNS.
My web server is (include version): Apache2.24
The operating system my web server runs on is (include version): Ubuntu 18.04.3
My hosting provider, if applicable, is: Hostinger
I can login to a root shell on my machine (yes or no, or I don’t know):yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 0.31.0
You use ns1.hostinger.com. Looks like Hostinger doesn't have an API. acme.sh supports a lot of dns providers - dnsapi · acmesh-official/acme.sh Wiki · GitHub - but it's the same: Not Hostinger.
So you can
use --manual, but you have to do that every 60 - 85 days
Thanks for the quick response. I also made a mistake in typing the command I entered “I missed out the --cert-name”.
I have succeeded in doing what I wanted by specifying only the subdomain I require as well as the original domain name and it appears to have worked adding the new subdomain and updating the original alancameron.net. But I am not sure it has. Is there a step after running certbot and getting the success message?