# Apache plugin for DNS

**URL:** <https://community.letsencrypt.org/t/apache-plugin-for-dns/108434>\
**Category:** Help\
**Created:** [December 11, 2019, 9:06pm UTC](https://community.letsencrypt.org/t/apache-plugin-for-dns/108434 "2019-12-11T21:06:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![macnala](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@macnala](https://community.letsencrypt.org/u/macnala)\
**Post date:** [December 11, 2019, 9:06pm UTC](https://community.letsencrypt.org/t/apache-plugin-for-dns/108434/1 "2019-12-11T21:06:50Z")

</div>

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](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.

My domain is: [alancameron.net](http://alancameron.net)

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

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [December 11, 2019, 9:14pm UTC](https://community.letsencrypt.org/t/apache-plugin-for-dns/108434/2 "2019-12-11T21:14:02Z")

</div>

Hi @macnala

> [@macnala](#):
>
> My domain is: [alancameron.net](http://alancameron.net)
> 
> I ran this command:sudo certbot certonly -d \*.alancameron.net

if you want to create a wildcard certificate, dns validation is required. But checking your domain - [https://check-your-website.server-daten.de/?q=alancameron.net](https://check-your-website.server-daten.de/?q=alancameron.net)

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](https://github.com/Neilpang/acme.sh/wiki/dnsapi) - but it's the same: Not Hostinger.

So you can

- use `--manual`, but you have to do that every 60 - 85 days
- switch to another dns server
- or use a CNAME and another dns provider

---

<div class="post-metadata">

**Author:** ![macnala](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@macnala](https://community.letsencrypt.org/u/macnala)\
**Post date:** [December 11, 2019, 9:38pm UTC](https://community.letsencrypt.org/t/apache-plugin-for-dns/108434/3 "2019-12-11T21:38:03Z")

</div>

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](http://alancameron.net). But I am not sure it has. Is there a step after running certbot and getting the success message?

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [December 11, 2019, 11:03pm UTC](https://community.letsencrypt.org/t/apache-plugin-for-dns/108434/4 "2019-12-11T23:03:13Z")

</div>

> [@macnala](#):
>
> 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](http://alancameron.net). But I am not sure it has.

Recheck your domain and see the CT log part.

If you have only one subdomain, you don't need a wildcard certificate.

Or use

```nohighlight
certbot certificates

```

to see your local certificates.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [January 10, 2020, 11:03pm UTC](https://community.letsencrypt.org/t/apache-plugin-for-dns/108434/5 "2020-01-10T23:03:13Z")

</div>

Closed on January 10, 2020, 11:03pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.