DNS Providers and Automatic HTTPS
Layer 10. Edge. Edge
SHC supports automatic DNS record management and HTTPS certificate issuance via integration with DNS providers and the daemon’s ACME source.
Overview
Section titled “Overview”When deploying apps with --expose (hostname), SHC can:
- Create DNS records pointing to your deployment
- Order an HTTPS certificate from the ACME provider, which Traefik serves
Configuration
Section titled “Configuration”DNS Provider Setup
Section titled “DNS Provider Setup”Configure DNS providers in your SHC config:
dns: providers: cloudflare: token: ref+vault://dns/cloudflare_token route53: region: us-east-1 access_key_id: ref+vault://dns/aws_access_key secret_access_key: ref+vault://dns/aws_secret_key # Optional: explicit default provider provider: cloudflareSupported Providers
Section titled “Supported Providers”| Provider | Config Key | Required Settings |
|---|---|---|
| Cloudflare | cloudflare | token |
| AWS Route53 | route53 | region |
| Hetzner | hetzner | token |
| PowerDNS | powerdns | api_key, endpoint |
| DigitalOcean | digitalocean | token |
| Google Cloud DNS | gcp | project_id |
| Azure DNS | azure | subscription_id, resource_group |
| Linode | linode | token |
| Vultr | vultr | api_key |
| Namecheap | namecheap | api_user, api_key, client_ip |
All providers support DNS-01 challenges automatically.
Provider Selection
Section titled “Provider Selection”If dns.provider is not set, SHC uses the first key in dns.providers.
CLI Usage
Section titled “CLI Usage”Basic Deployment with DNS
Section titled “Basic Deployment with DNS”# Create DNS record pointing to current nodeshc install nginx --expose app.example.comPublic HTTPS
Section titled “Public HTTPS”# A public route's certificate comes from the ACME provider once acme.* is setshc install nginx --expose app.example.com --publicOverride DNS Provider
Section titled “Override DNS Provider”# Use specific provider for this deploymentshc install nginx --expose app.example.com --dns-provider route53DNS Cleanup on Uninstall
Section titled “DNS Cleanup on Uninstall”# Uninstall releases the deployment's managed-DNS records automaticallyshc uninstall myappTLS Modes
Section titled “TLS Modes”Every routed hostname gets a certificate from the tenant’s own CA. A
public route gets one from the ACME provider once acme.* is set, and the
hostname’s zone picks the challenge. No flag does.
HTTP-01 Challenge
Section titled “HTTP-01 Challenge”When no DNS connection of the tenant owns the hostname’s zone:
- Domain must resolve to the Traefik instance
- Port 80 must be accessible from the internet
DNS-01 Challenge
Section titled “DNS-01 Challenge”When a DNS connection of the tenant owns the hostname’s zone:
- DNS provider credentials must be configured
- Required for wildcard certificates
Record Types
Section titled “Record Types”SHC automatically selects the appropriate DNS record type:
| Target Type | Record Type |
|---|---|
| IPv4 address | A |
| IPv6 address | AAAA |
| Hostname | CNAME |
Scope Resolution
Section titled “Scope Resolution”DNS provider selection follows the scope ladder, narrowest first (ce core/scope/scope.go, Cascade). Stack outranks environment. There is no base tier; the broadest tier is global.
--dns-provideron the commanddns.providerat deployment scope (tenant + stack + environment)dns.providerat stack scope (tenant + stack)dns.providerat environment scope (tenant + environment)dns.providerat tenant scopedns.providerat global scope- First key in
dns.providerswhen no row is set
Traefik Integration
Section titled “Traefik Integration”Traefik runs no ACME client and holds no DNS provider credential. The daemon’s ACME source orders each certificate once and every Traefik replica serves it. See Networking.
ACME Email
Section titled “ACME Email”Configure contact email for Let’s Encrypt notifications:
acme:Staging Certificates
Section titled “Staging Certificates”For testing, use Let’s Encrypt staging:
acme: staging: trueBest Practices
Section titled “Best Practices”- Use DNS-01 for internal services: Avoids exposing port 80
- Store credentials in Vault: Use
ref+vault://references - Set ACME email: Receive certificate expiration warnings
- Test with staging first: Avoid rate limits during development