Dns-01 Update Method with SimpleDNS

Question
1

I"m attempting to set up the automatic renewal and using SimpleDNS. On SimpleDNS I have the http API enabled with Digest as the authenication.

When I attempt to input the information info the crednetials of Certify the Web I ended up always getting an error.

I entered in the servers IP address (192.168.100.100), auth key as the “User ID” from SimpleDNS, and auth secret as the “password” from SimpleDNS

The error that I get back is check credentials are correctly set when I attempt to pull back the DNS Zone ID.

What is it that I am missing or doing wrong?

2

Hi,

Our SimpleDNS api provider was user contributed and as such I don’t have a test server for this however I’ve downloaded a test copy and had a look at the UI, the configuration required appears to be quite specific (not the default):

The current provider code expects to construct the API call as `https://ip:port/v2/ so you need:
https setup for your API.

Once you can browse to the SimpleDNS API in a browser OK then the rest of the API should work. e.g.: https://yourdomain.com:8053/v2/swagger.json

That said, in my tests I have been unable to get the API integration to work and I will now have to consider whether we will attempt to fix it or remove it completely. As a workaround I recommend either using http validation instead of DNS, or switching DNS provider (such as cloudflare or route53), or try acme-dns (which currently requires setting up your own acme-dns server).

3

If you need anyone for beta testing please let me know. I am more then willing to.

I would love the functionality to be fixed and continued to be support. SimpleDNS is an amazing product.

Well I will give it a try and see if I can get it to work with the software. I’m somewhat familiar with the SimpleDNS API because I am using it in a couple of our internal applications to make DNS changes on the fly and without user interaction.

4

Thanks, other point I missed was you need to set authentication to basic. The main problems I found were the zone results are not populated properly (although you can just type your zone name) and domains with 2 tld levels don’t work (like .co.uk)

5

Hi, really like/want/need this to work. Have figured it all out now and got it working. Am really stuck on the 2 tld issue. Have tested with a 1 tld and works perfectly. I have a dev team here, so will happily tweak that code block to resolve that bug if you are happy with that?

Mat

6

Hi, I wasn’t actually aware this was still a problem - forums are awful bug trackers (we have GitHub issues).

If you have an urgent requirement for a certificate you can:

-temporarily switch to the manual DNS update method

  • or use the default acme-dns service
  • or switch to a better supported DNS provider like away route 53 or CloudFlare.

I’m assuming this is not urgent (as in needs resolves today) as Let’s Encrypt just broke 26 million certs and I have my hands full. You can definitely try building the code from GitHub - the usual fix for tld levels is to use the base DNS provider class which has a common method for tld traversal.

7

Regarding the 2 tld issue, I’ve prepared an experimental fix for this in v5 (which now also includes many more DNS providers courtesy of the Posh-ACME project), I’m hoping to get to a beta release for users to test with during April.