-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Add new dnsapi support for OpenProvider.eu using new REST API #6123
base: dev
Are you sure you want to change the base?
Conversation
Welcome |
As a result of PR #6111 updated the script to be a new dnsapi instead of replacing the older (but still working) version. Changed to dns_openprovider_rest as suggested. Pending new entry with anchor in /wiki/dnsapi2 once approved. |
CC @TheLastProject @Ritbit @WinSCaP could you review and test? |
Sorry, but I no longer work at the place I used to work where they used OpenProvider and don't have any domains with OpenProvider myself, so I have no domains I could possibly test this with anymore |
As i did notice PR specs changed last couple of weeks and are more detailed. Just added new entry to dnsapi2 to make the "checklist" complete for the PR. |
@Neilpang yes, actions are enabled and the secrets also present with right values to allow tests to run. Re-triggered the flow just by syncing the fork with current state, so it's pending workflow approval again. Initial run after the commit indicates an issue on the Docker clone/run; |
the test should run in your repo: |
This add support for OpenProvider.eu / .com using their newer REST API.
With this newer version there is no full DNS zone update needed anymore (including existing A, AAAA, CAA, CNAME, MX, NS, PTR, SOA, SRV, and TXT) for a single validation request.
Only the single TXT record is added and removed for the validation request.
_Note: added as new dnsapi option as the original SOAP/XML API is still online and working with dns_openprovider.sh