DNS Providers
Connect your DNS provider for automatic domain verification and certificate management.

Overview
DNS provider integration enables:
- Automatic domain verification - DNS-01 challenges for SSL certificates
- Wildcard certificates - Secure all subdomains
- Faster verification - No manual DNS record creation
- Real-time status monitoring - Track synchronization and detect issues instantly
Supported Providers
| Provider | API Support | Wildcard Certs |
|---|---|---|
| Cloudflare | ✓ | ✓ |
| AWS (Route 53) | ✓ | ✓ |
| DigitalOcean | ✓ | ✓ |
| OVH | ✓ | ✓ |
| Gandi | ✓ | ✓ |
| GoDaddy | ✓ | ✓ |
| Azure DNS | ✓ | ✓ |
| IONOS | ✓ | ✓ |
| Scaleway | ✓ | ✓ |
Adding a DNS Provider
Steps
- Go to your project
- Click Settings in the project sidebar
- Select the DNS Providers tab
- Click Add Provider
- Select your provider
- Enter API credentials
- Click Save
Provider Configuration
Cloudflare
Required credentials:
- API Token (recommended) or
- Global API Key + Email
Creating an API Token:
- Go to Cloudflare Dashboard
- Click Create Token
- Use template: Edit zone DNS
- Select your zone
- Create and copy token
Token: <your-cloudflare-api-token>
Permissions needed:
- Zone → DNS → Edit
- Zone → Zone → Read
Optional settings:
- Enable Cloudflare Proxy - Route traffic through Cloudflare's CDN and security features
AWS (Route 53)
Required credentials:
- Access Key ID
- Secret Access Key
IAM Policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"route53:GetChange",
"route53:ChangeResourceRecordSets",
"route53:ListResourceRecordSets"
],
"Resource": [
"arn:aws:route53:::hostedzone/ZONE_ID",
"arn:aws:route53:::change/*"
]
},
{
"Effect": "Allow",
"Action": "route53:ListHostedZones",
"Resource": "*"
}
]
}
DigitalOcean
Required credentials:
- Personal Access Token
Creating Token:
- Go to DigitalOcean API
- Generate new token
- Grant: Read and Write
Token: <your-digitalocean-token>
OVH
Required credentials:
- Application Key
- Application Secret
- Consumer Key
Creating an OVH API Token:
- Go to OVH API Token Creation
- Fill in the application details:
- Application name: SailOps DNS Management (or your preferred name)
- Application description: DNS management for SailOps custom domains
- Set the required API permissions (rights):
| Method | Path | Description |
|---|---|---|
GET | /domain/zone | List available zones |
GET | /domain/zone/*/record | List DNS records in a zone |
GET | /domain/zone/*/record/* | Get specific record details |
PUT | /domain/zone/*/record/* | Update existing DNS records |
POST | /domain/zone/*/record | Create new DNS records |
DELETE | /domain/zone/*/record/* | Remove DNS records |
GET | /domain/zone/*/soa | Get SOA record information |
POST | /domain/zone/*/refresh | Apply DNS changes |
Copy-paste format for easy OVH API token creation:
GET /domain/zone
GET /domain/zone/*/record
GET /domain/zone/*/record/*
PUT /domain/zone/*/record/*
POST /domain/zone/*/record
DELETE /domain/zone/*/record/*
GET /domain/zone/*/soa
POST /domain/zone/*/refresh
- Set Validity: Choose your preferred duration (e.g., "Unlimited" for permanent access)
- Click Create keys
- Copy the generated credentials:
- Application Key (AK)
- Application Secret (AS)
- Consumer Key (CK)
Important Notes:
- These permissions are the minimum required for SailOps to manage DNS records
- The
*wildcard allows access to all your domain zones - You can restrict access to specific zones by replacing
*with your domain name (e.g.,/domain/zone/example.com/record) - Keep your credentials secure and never share them publicly
Gandi
Required credentials:
- API Key (Personal Access Token)
Creating Token:
- Go to Gandi Account
- Security → Personal Access Tokens
- Create with DNS permissions
Azure DNS
Required credentials:
- Subscription ID
- Tenant ID
- Client ID
- Client Secret
- Resource Group Name
Creating Service Principal:
az ad sp create-for-rbac \
--name "SailOps-DNS" \
--role "DNS Zone Contributor" \
--scopes /subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.Network/dnszones/{zone}
Getting Resource Group Name:
The Resource Group Name is the name of the Azure Resource Group containing your DNS Zone. You can find it in the Azure Portal under your DNS Zone's overview page.
GoDaddy
Required credentials:
- API Key
- API Secret
Getting Credentials:
- Go to GoDaddy Developer Portal
- Create an API Key
- Select Production environment
- Copy API Key and Secret
IONOS
Required credentials:
- API Key
Getting Credentials:
- Go to IONOS Developer Portal
- Navigate to API Keys section
- Create a new API key with DNS permissions
- Copy the API key
Scaleway
Required credentials:
- Access Key (API Key)
- Secret Key
Getting Credentials:
- Go to Scaleway Console
- Navigate to IAM → API Keys
- Create a new API key
- Copy Access Key and Secret Key
Using DNS Providers
Domain Verification
When adding a custom domain:
- SailOps detects matching DNS provider
- Automatically creates verification records
- Requests SSL certificate
- Cleans up temporary records
Without DNS Provider
If no provider is configured:
- Manual DNS record creation required
- HTTP-01 challenge used (no wildcards)
- Longer verification time
Managing Providers
Viewing Providers
- Go to Settings in the project sidebar
- Select the DNS Providers tab
- See all configured providers and managed zones
Testing Connection
- Click Test on a provider
- SailOps verifies API access
- Lists accessible zones
Updating Credentials
- Click on the provider
- Update API credentials
- Click Save
Removing a Provider
- Click Delete
- Confirm removal
Removing a provider doesn't affect existing certificates but prevents automatic renewal.
Provider Status Monitoring
SailOps provides real-time status monitoring for your DNS providers, helping you quickly identify and resolve configuration issues.
Status Indicators
Each DNS provider displays a status badge indicating its current state:
| Status | Badge | Description |
|---|---|---|
| Healthy | 🟢 Green | Provider is working correctly. DNS records are being synchronized. |
| Syncing | 🔵 Blue | Provider is starting up or currently synchronizing records. |
| Error | 🔴 Red | Provider has encountered an error. Check the error details for more information. |
Status Information
When you view a DNS provider, you'll see:
- Status Badge - Current synchronization state
- Last Sync Time - When the provider last attempted to synchronize
- Last Successful Sync - When records were last successfully updated
- Managed Records Count - Number of DNS records currently managed
Error Types
When a provider encounters an error, SailOps categorizes it to help you troubleshoot:
| Error Code | Description | Common Causes |
|---|---|---|
| Authentication Failed | API credentials are invalid or expired | Invalid API key, expired token, revoked access |
| Permission Denied | Credentials lack required permissions | Missing DNS edit permissions, zone access restricted |
| Rate Limited | Too many API requests | High frequency of DNS changes, provider rate limits |
| Network Error | Cannot connect to provider API | Provider outage, connectivity issues, TLS/certificate errors |
| API Error | Provider API returned an error | Provider service issues (500, 502, 503, 504 errors) |
| Configuration Error | Provider configuration is invalid | Zone not found, invalid zone configuration, domain mismatch |
Resolving Status Issues
Authentication Failed
- Verify your API credentials are correct
- Check if credentials have expired or been revoked
- Regenerate credentials from your DNS provider's dashboard
- Update credentials in SailOps
Permission Denied
- Review the required permissions for your provider (see Provider Configuration)
- Update your API credentials to include necessary permissions
- For limited-scope credentials, ensure they have access to the correct zones
Rate Limited
- Wait for the rate limit window to reset (usually 1-5 minutes)
- If persistent, reduce the frequency of domain changes
- Consider consolidating domains under wildcard certificates
Network Error
- Check if your DNS provider is experiencing an outage
- Verify the provider's API endpoint is accessible
- If using TLS/certificates, ensure they are valid
Configuration Error
- Verify the domain zone exists in your DNS provider
- Check that the zone name matches exactly
- Ensure your API credentials have access to the specific zone
Automatic Recovery
SailOps automatically attempts to recover from transient errors:
- Network errors: Retried automatically with exponential backoff
- Rate limits: Requests are throttled and retried after the limit resets
- API errors: Retried for temporary server issues (5xx errors)
For persistent errors (authentication, permissions, configuration), manual intervention is required.
Zone Management
Automatic Zone Detection
SailOps automatically detects zones when:
- Domain matches provider zone
- API has zone access
Multiple Zones
One provider can manage multiple zones:
Zone Conflicts
If multiple providers manage the same zone:
- First matching provider is used
- Order in settings determines priority
Security Best Practices
1. Minimal Permissions
Create dedicated credentials with limited scope:
✓ Only DNS read/write access
✓ Only specific zones
✓ Dedicated service account
✗ Admin/Owner access
✗ All zones access
✗ Shared credentials
2. Credential Rotation
Rotate API credentials regularly:
- Every 90 days recommended
- After team member changes
- After security incidents
3. Audit Logging
Monitor DNS changes:
- Review provider audit logs
- Set up alerts for unexpected changes
- Track certificate issuance
Troubleshooting
Check the Provider Status indicator first! The status badge and error details often provide immediate insight into the problem. See Provider Status Monitoring for details.
Verification Failed
Error: DNS verification timeout
- Check provider credentials are valid
- Verify zone is accessible
- Check for DNS propagation (wait 5-10 minutes)
Error: Zone not found
- Verify domain matches zone exactly
- Check API has access to zone
- Ensure zone exists in provider
Error: Permission denied
- Review API permissions
- Add missing scopes
- Recreate credentials if needed
Certificate Issues
Error: CAA record prevents issuance
Add CAA record for Let's Encrypt:
example.com. CAA 0 issue "letsencrypt.org"
Error: Rate limit exceeded
Let's Encrypt limits:
- 50 certificates per domain per week
- 5 duplicate certificates per week
Solutions:
- Wait for rate limit reset
- Use wildcard certificates
- Consolidate subdomains
Provider-Specific Issues
Cloudflare: Proxy conflict
Disable Cloudflare proxy (orange cloud) for verification:
- SailOps creates records with proxy disabled
- After verification, you can enable proxy
AWS: Region mismatch
Route 53 is global, but ensure:
- Correct AWS region in credentials
- Hosted zone ID matches domain