-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added dns_doapi.sh #2053
Added dns_doapi.sh #2053
Conversation
please check every item of this guide: and make sure your can handle v2 wildcard domain. |
Apart from the fact that my name is dns_doapi.sh instead of doapi.sh (like it suggets in #2 of the guide), I think it follows all the guidelines. It can handle v2 wildcard domains. I've successfully issued such a certificate. |
I don't think so. please make sure you can handle all the domains:
please update your dns in the supported list: |
Hi, it can handle all these domains. The hoster API automatically handles that, and only needs to be provided with the FQDN. The API is already on the supported list as "Domain-Offensive/Resellerinterface/Domainrobot API". Don't need to mention it twice. |
Ok, please add it to the list still. So that the list count keep same as the count in the dnsapi readme. 60. do.de API In the dns api readme, please move to Thanks. |
Sure, just did that :) Thanks! |
OK. Report bug to do.de dns api And watch to that issue, if in future any bug is found, it will be reported there. Thanks. |
OK, created #2057 and followed the issue 😄 |
Hi,
this new adapter adds support for the official LE API for the domain hosting company do.de.
There is already support in acme.sh in the dns_do.sh adapter, but this API has some downsides:
The new API is explicitly meant to set _acme-challenge records and provides authentication via a token mechanism.
If you want to test this API, I will gladly send you a (test) token. Just tell me a mail address to send it to.
The plugin was written according to the dev guidelines and also supports wildcard certifiates.
PS: I'm not 100% sure about the naming, but I didn't want to break compatibilty with the existing API. Suggestions for a different filename are welcome.
Thanks,
Tobias