Recipes
A recipe joins several API calls into one complete workflow: with prerequisites, waiting logic, rollback and the pitfalls you would otherwise only find on the second attempt. At the end of every recipe sit the endpoints it uses and the matching place in the interface.
Maintaining DNS
Section titled “Maintaining DNS”| Goal | Recipe |
|---|---|
| New servers get their records in one go | Prepare new hosts |
| The zone follows a file in the repo | DNS desired state |
| A change you can take back | DNS change with rollback |
Keeping IP addresses current
Section titled “Keeping IP addresses current”| Goal | Recipe |
|---|---|
| A server updates its own IP | DynDNS URL update |
| The home connection reports itself | DynDNS with the FRITZ!Box |
Automating certificates
Section titled “Automating certificates”| Goal | Recipe |
|---|---|
| Everything automatic, one tool | Automate with certbro |
| Self built over the API, with DNS validation | TLS with DNS DCV |
| Renew one certificate deliberately | TLS renewal |
| Stretch lifetime through reissues | Reissue cycle |
| Watch orders and cancel stuck ones | Monitor and cancel |
| Inventory and back up the stock | Inventory and export |
| Replace a compromised certificate | Revoke and replace |
| OV certificate with organization validation, via API | OV order with org ID |
| OV certificate with organization validation, via certbro | OV with certbro |
Before you start
Section titled “Before you start”Every recipe names its own prerequisites. Two always apply: an API key with the permissions named there, and the basics from getting started.