Do you have support for wild card certs? If not when?
Yes, we are currently testing our v4 alpha version, see this thread: Join the v4 alpha/beta testing!
Like all tools using Let’s Encrypt this will require that you use DNS validation instead of http, which means you need a DNS provider with an API. Currently we support Azure DNS, cloudflare and AWS Route 53.
This makes no sense. To get a free wild card cert you need to pay for a DNS service. More like let’s not encrypt.
That’s Let’s Encrypts decision, but cloudflare at least has a pretty good free plan.
I’ve found that running any kind of server incurs costs, especially a dedicated windows server/vm.
I would like to vote for DNSMadeEasy support for the DNS validation. Where can I cast my vote? 
They’ve got an API.
We have a number of internal servers that we want to install certs on. They are not publicly accessible (nor do we want them to be), so we can’t use the regular HTTP validation. If we could do DNS validation, we could setup all our servers using Let’s Encrypt, and we’d be happy to be paying customers!
1 Like
Quote: “This makes no sense. To get a free wild card cert you need to pay for a DNS service. More like let’s not encrypt.”
Also bear in mind that compared to buying even a one-year wildcard SSL certificate, the cost of paying for DNS services is negligible (pennies for millions of look ups).
The Azure costs are here: https://azure.microsoft.com/en-us/pricing/details/dns/
If you have a single DNS zone, it’s less than 1 US dollar per month for a million queries…where else can you get a wildcard cert for less than US$12 a year?
And that’s before you consider the free Cloudflare DNS option.
1 Like