DNS providers
A provider is an account at the host of your DNS zones, with the credentials that let local-cert write there. This is how the proof Let's Encrypt asks for gets published: a TXT record set for the duration of the validation.
Supported hosts
| Host | Service | Credentials | Minimum TTL | Guide |
|---|---|---|---|---|
| AWS | Route53 | IAM key, role recommended | 30 s | open |
| OVHcloud | OVHcloud DNS zones | API region, Application key, Application secret, Consumer key | 60 s | open |
| Gandi | LiveDNS | Personal Access Token | 300 s | open |
| GoDaddy | GoDaddy DNS | API key, API secret | 600 s | open |
| Google Cloud | Cloud DNS | Service account key (JSON) | 1 s | open |
The principle, whichever host you use
- At the host, you create credentials limited to DNS — never those of your main account.
- Providers → + New provider: you pick the host, paste the credentials, test, save.
- Domains → + Add a domain: local-cert lists the account's zones, you pick one, and it tests its permissions.
Several providers on the same host is the normal case: one per account, or one per permission scope. Secrets are encrypted in the database (AES-256-GCM with MASTER_KEY) and are never displayed again or returned by the API.
What differs from one host to another
| AWS Route53 | The others | |
|---|---|---|
| Permissions | per zone: an IAM policy to extend with every domain added | carried by the credentials: nothing to change when you add a domain |
| Permission test | no write at all in the zone | a temporary TXT record (_localcert-preflight-…) is created and then deleted |
| Writes | atomic, tracked until propagation | record by record |
Marking what local-cert creates
Every record published at your request comes with a TXT _local-cert.<name>: this is what lets you tell, in the zone, what comes from local-cert from what was already there. Setting TAG_RECORDS=0 turns it off.
Declaring a provider with environment variables
When credentials must come from the deployment rather than the database, a provider can be declared with variables. This is optional, and the block is repeated with a different label for each account.
# PROVIDER_<HOST>_<LABEL>_NAME declares the provider; the rest are its credentials
PROVIDER_AWS_DEFAULT_NAME="Default AWS"
PROVIDER_AWS_DEFAULT_ACCESS_KEY_ID=AKIA…
PROVIDER_AWS_DEFAULT_SECRET_ACCESS_KEY=…
PROVIDER_AWS_DEFAULT_ROLE_ARN=arn:aws:iam::123456789012:role/local-cert-dns
PROVIDER_OVH_PERSO_NAME="ovh-perso"
PROVIDER_OVH_PERSO_ENDPOINT=ovh-eu
PROVIDER_OVH_PERSO_APPLICATION_KEY=…
PROVIDER_OVH_PERSO_APPLICATION_SECRET=…
PROVIDER_OVH_PERSO_CONSUMER_KEY=…
PROVIDER_GANDI_MAIN_NAME="gandi"
PROVIDER_GANDI_MAIN_TOKEN=…
PROVIDER_GODADDY_MAIN_NAME="godaddy"
PROVIDER_GODADDY_MAIN_API_KEY=…
PROVIDER_GODADDY_MAIN_API_SECRET=…
PROVIDER_GCP_MAIN_NAME="gcp"
PROVIDER_GCP_MAIN_SERVICE_ACCOUNT_JSON=<the key's JSON, or its base64 encoding>
PROVIDER_GCP_MAIN_PROJECT_ID=my-project # optional- The label (
DEFAULT,PERSO,MAIN…) is free: uppercase letters, digits and underscores. - These providers appear in the console with an environment tag. They can be tested, but not edited or removed: that is done in the variables, followed by a restart. Their secrets are never written to the database.
- An incomplete declaration is ignored, with a message at startup naming the missing variable.