Support for provider: Rackcorp
Author: jstangroomeCreated May 18, 2026Updated Sep 11, 2026
Labelsenhancementwaiting-for/user-testswaiting-for/contrib-feedbacknew-provider
Welcome
- Yes, I've searched for similar issues on GitHub and didn't find any.
- Yes, the DNS provider has a documented API.
- Yes, I know that the lego maintainers don't have an account in all DNS providers in the world.
Implementation
- Yes, I'm able to create a pull request and be able to maintain the implementation.
- Yes, I can test an implementation with the help of the maintainers if someone creates a pull request.
Link to the DNS provider
Link to the API documentation
https://github.com/RackCorpCloud/rackcorp-api/wiki/RACKCORP-REST-API
Additional Notes
Already implemented in branch linked below, ready to become a Pull Request if appropriate: https://github.com/jstangroome/go-acme-lego/tree/jstangroome-rackcorp-dns-provider2
Implementation was based on the existing DNSimple and NS1 implementations and does not introduce any new dependencies.
Changes have been verified with make generate, make checks, make build, and make test.
Live testing has also been performed with:
RACKCORP_API_UUID=... \
RACKCORP_API_SECRET=... \
RACKCORP_DOMAIN=... \
make testHow do you use lego?
Through Traefik
Who are you?
Employee of this DNS provider
In which context are you using lego?
Professional use
Supporting the Maintainer
- Yes, I find this project useful, and it has saved me time in my workflow/business.
- Yes, I have starred this repository to help others find it.
- Yes, I have sponsored this project to keep the project stable and maintained.
Confirmation
- Yes, I've included all the information above (links, notes, etc.).
Source: go-acme/lego