GoDaddy provider
local-cert manages GoDaddy DNS with a production API key. First check that your account is eligible: GoDaddy doesn't open the API to everyone.
1. Create the key
- Open
https://developer.godaddy.com/keys, logged in to the account that holds the domains. - Create New API Key. Name:
local-cert. Environment: Production (an OTE key doesn't see your real domains). - Copy the Key and the Secret: the secret is displayed only once.
A GoDaddy key gives access to the whole account: there is no restriction by domain or by type of operation.
2. Create the provider
- Providers → + New provider → GoDaddy.
- Give it a name, paste the key and the secret.
- Test connection, then Save.
3. Add a domain
Domains → + Add a domain → this provider → the domain. The test creates and then deletes a temporary TXT record.
Good to know
- The domain must use GoDaddy's name servers (
ns*.domaincontrol.com). - Minimum TTL: 600 seconds. local-cert raises any lower value. This has no effect on certificate issuance.
If your account has no API access
Keep the domain at GoDaddy and delegate only your local network's subdomain to a host that local-cert can manage:
- Create a
home.example.comzone at AWS Route53, OVHcloud, Gandi or Google Cloud DNS. - In GoDaddy's DNS for
example.com, add oneNSrecord per name server of that zone, with the namehome. - Declare the matching provider and add the delegated domain.
Troubleshooting
| Message | Cause |
|---|---|
401 UNABLE_TO_AUTHENTICATE | Wrong key or secret, or an OTE key used in production. |
403 ACCESS_DENIED | The account doesn't meet the API access requirement. |
422 on write | Value rejected by GoDaddy (TTL, format): the message names the field. |