Skip to content
SHC Docs

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.

When deploying apps with --expose (hostname), SHC can:

  1. Create DNS records pointing to your deployment
  2. Order an HTTPS certificate from the ACME provider, which Traefik serves

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: cloudflare
ProviderConfig KeyRequired Settings
Cloudflarecloudflaretoken
AWS Route53route53region
Hetznerhetznertoken
PowerDNSpowerdnsapi_key, endpoint
DigitalOceandigitaloceantoken
Google Cloud DNSgcpproject_id
Azure DNSazuresubscription_id, resource_group
Linodelinodetoken
Vultrvultrapi_key
Namecheapnamecheapapi_user, api_key, client_ip

All providers support DNS-01 challenges automatically.

If dns.provider is not set, SHC uses the first key in dns.providers.

Terminal window
# Create DNS record pointing to current node
shc install nginx --expose app.example.com
Terminal window
# A public route's certificate comes from the ACME provider once acme.* is set
shc install nginx --expose app.example.com --public
Terminal window
# Use specific provider for this deployment
shc install nginx --expose app.example.com --dns-provider route53
Terminal window
# Uninstall releases the deployment's managed-DNS records automatically
shc uninstall myapp

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.

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

When a DNS connection of the tenant owns the hostname’s zone:

  • DNS provider credentials must be configured
  • Required for wildcard certificates

SHC automatically selects the appropriate DNS record type:

Target TypeRecord Type
IPv4 addressA
IPv6 addressAAAA
HostnameCNAME

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.

  1. --dns-provider on the command
  2. dns.provider at deployment scope (tenant + stack + environment)
  3. dns.provider at stack scope (tenant + stack)
  4. dns.provider at environment scope (tenant + environment)
  5. dns.provider at tenant scope
  6. dns.provider at global scope
  7. First key in dns.providers when no row is set

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.

Configure contact email for Let’s Encrypt notifications:

acme:

For testing, use Let’s Encrypt staging:

acme:
staging: true
  1. Use DNS-01 for internal services: Avoids exposing port 80
  2. Store credentials in Vault: Use ref+vault:// references
  3. Set ACME email: Receive certificate expiration warnings
  4. Test with staging first: Avoid rate limits during development